ARA-C01 Question 319
Single answerAPI endpointsA global retailer is standardizing how internal applications interact with Snowflake. The architecture team wants application teams to invoke SQL statements over HTTPS without managing JDBC/ODBC drivers, and they also need a programmatic way to poll statement status and retrieve results for long-running requests. Which Snowflake API endpoint best fits this requirement?
- A
The SQL API endpoint, which allows submitting SQL statements over REST and checking statement execution status/results
- B
The Snowpipe REST endpoint, because it accepts HTTPS requests and can be used to execute arbitrary SQL asynchronously
- C
The Query History endpoint in Snowsight, because it exposes execution state and result retrieval for application integration
- D
The JDBC connection endpoint, because JDBC is Snowflake's REST-based API for stateless SQL execution over HTTPS
Show answer and explanation
Correct answer: A
Explanation
The key requirement is driverless SQL execution over HTTPS with support for asynchronous processing, statement status checks, and result retrieval. Snowflake's SQL API is the correct fit for this use case. It is specifically intended for applications that need to submit SQL statements via REST without relying on JDBC or ODBC drivers. By contrast, Snowpipe REST APIs are limited to ingestion workflows, and Snowsight query history is not an integration endpoint. Snowflake documentation for the SQL API describes submitting statements, handling long-running operations, and retrieving results via REST endpoints, which directly matches the scenario.
- A. Correct.
Correct. Snowflake SQL API is designed for executing SQL statements through HTTPS REST calls. It supports submitting statements, checking execution status, and retrieving results, making it suitable for driverless application integration and for handling long-running queries programmatically.
- B. Incorrect.
Incorrect. Snowpipe REST endpoints are for data ingestion operations such as loading files into tables, not for executing arbitrary SQL statements. Although Snowpipe uses HTTPS, it does not replace the SQL API for general-purpose query execution.
- C. Incorrect.
Incorrect. Query History in Snowsight is an interface feature for monitoring and reviewing executed queries, not a supported application-facing API endpoint for submitting SQL and polling results. This option confuses a UI capability with an integration API.
- D. Incorrect.
Incorrect. JDBC is a database connectivity driver/protocol, not the Snowflake REST SQL endpoint described in the scenario. It requires client driver management, which the architecture team specifically wants to avoid.