Amazon Redshift Data API for Real-Time Queries

DEA-C01 By islever Editorial Last updated

Automate data processing by using AWS services.

Short answer

B Use the Amazon Redshift Data API to execute SQL queries directly via HTTPS without managing persistent connections or drivers.

Question

A financial services company stores financial data in Amazon Redshift. A data engineer wants to run real-time queries on the financial data to support a web-based trading application. The data engineer wants to run the queries from within the trading application. Which solution will meet these requirements with the LEAST operational overhead?
  1. Establish WebSocket connections to Amazon Redshift.
  2. Use the Amazon Redshift Data API. Correct Answer
  3. Set up Java Database Connectivity (JDBC) connections to Amazon Redshift.
  4. Store frequently accessed data in Amazon S3. Use Amazon S3 Select to run the queries.

Key Takeaways

This question tests the ability to select the most lightweight integration method for Amazon Redshift; the common trap is choosing traditional JDBC/ODBC which requires significant connection management overhead compared to the managed Data API.

The Amazon Redshift Data API provides a serverless, HTTPS-based interface for executing SQL queries, eliminating the need to manage database drivers or persistent connections. This solution offers the least operational overhead for web-based applications querying financial data in real-time.

Common mistake: Candidates often select JDBC (Option C) because it is the standard way to connect to databases, failing to recognize that managing persistent connections and driver updates constitutes higher operational overhead than using the managed Data API.

Expert Analysis

Why the Answer Is Correct

The Amazon Redshift Data API is specifically designed to reduce operational overhead by providing a serverless HTTP endpoint for executing SQL commands. It handles connection pooling, authentication via IAM, and query execution without requiring the client application to maintain persistent TCP connections or install specific drivers like JDBC/ODBC. For a web-based trading application requiring real-time access, this matches the requirement for "least operational overhead" perfectly.

Why the Other Options Are Wrong

Option A is incorrect because Amazon Redshift does not natively support WebSocket connections for SQL queries. Option C (JDBC) requires managing network plumbing, driver versions, and connection lifecycle, which increases operational burden. Option D involves moving data to S3 and using S3 Select, which changes the data store entirely and likely introduces latency inconsistent with real-time requirements on the existing Redshift cluster.

Community Comment Notes

Community consensus strongly supports Option B, with users noting that the Data API eliminates the need to manage persistent database connections. As one commenter paraphrased, it allows interaction without maintaining network plumbing or JDBC drivers, highlighting the efficiency gain. Another user explicitly stated that while JDBC is possible, the Data API is correct for minimizing effort inside an application.

Official Reference

https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

When asked for the "least operational overhead" for database interactions, prioritize managed services like APIs over direct driver-based connections (JDBC/ODBC), as they abstract away infrastructure maintenance tasks.

Frequently Asked Questions

Why not use JDBC for real-time queries?

JDBC requires managing connection pools, driver updates, and network configuration, which increases operational overhead compared to the serverless Data API.

Does Redshift support WebSockets?

No, Amazon Redshift does not support native WebSocket connections for SQL queries; it relies on JDBC/ODBC or the Data API.

More DEA-C01 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 11 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 11

  1. TonyStark0122 👍 4
    B. Use the Amazon Redshift Data API. Explanation: The Amazon Redshift Data API is a lightweight, HTTPS-based API that provides an alternative to using JDBC or ODBC drivers for running queries against Amazon Redshift. It allows you to execute SQL queries directly from within your application without the need for managing connections or drivers. This reduces operational overhead as there's no need to manage and maintain WebSocket or JDBC connections.
  2. milofficial 👍 4 Answered B
    Real time queries with S3 are obviously BS. B it is: https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html
  3. DevoteamAnalytix 👍 3 Answered B
    "The Amazon Redshift Data API enables you to painlessly access data from Amazon Redshift with all types of traditional, cloud-native, and containerized, serverless web service-based applications and event-driven applications." https://aws.amazon.com/de/blogs/big-data/using-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-clusters/#:~:text=The%20Amazon%20Redshift%20Data%20API%20is%20not%20a%20replacement%20for,supported%20by%20the%20AWS%20SDK.
  4. GiorgioGss 👍 3 Answered B
    Even if you don't know nothing about them, you will still choose B because it seems the "LEAST operational overhead" :)
  5. bhawna901 👍 2
    Amazon Redshift Data API: Provides a serverless and simple HTTP-based API to interact with Redshift. Ideal for web-based applications since it eliminates the need to manage persistent database connections (like JDBC or ODBC). Allows the trading application to send queries directly to Redshift using HTTPS requests, making it easy to integrate with modern applications. Removes the complexity of managing database connection pooling in real-time, which reduces operational overhead. Securely integrates with IAM roles and policies for authentication and access control.
Show 6 more comments
  1. k350Secops 👍 2 Answered B
    Inside application with minimal effort then using API would be correct
  2. ninomfr64 👍 1 Answered B
    You can query a Redshift cluster with either JDBC/ODBC or Data API. The latter just requires you to maintain AWS SDK and IAM role, while the former needs network plumbing to access VPC, JDBC/ODBC driver, database credentials possibly stored in Secret Manager
  3. markill123 👍 1 Answered B
    A) Redshift doesn't support WebSockets; C) It is way harder to manage DB connections than using Redshift Data API which will offer you the possibility to run SQL queries directly. D)
  4. Palee 👍 1 Answered B
    Most efficient solution
  5. Scotty_Nguyen 👍 1 Answered B
    B is correct
  6. Alcee 👍 1
    B. DATA API

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Amazon Redshift Compound Sort Key Query Optimization

S-grade

Secure Redshift Spectrum Access with VPC Endpoints

S-grade

Athena Federated Query for Multi-Source Iceberg Pipelines

S-grade

Reclaiming Storage in Amazon Redshift Materialized Views

S-grade

Practice All DEA-C01 Questions

Access 100 questions with complete answers and detailed explanations.

View Full DEA-C01 Practice Test →

← Back to DEA-C01 Study Guide