ARA-C01 Question 309
Single answerSnowflake Connector for ServiceNowA global enterprise uses ServiceNow for IT service management and Snowflake as its analytics platform. The architecture team is evaluating the Snowflake Connector for ServiceNow to make incident, change, and request data available in Snowflake with minimal custom development. Security requires encrypted connectivity and controlled credentials, while the analytics team wants a supported approach that can be scheduled and operated by ServiceNow administrators rather than building custom ETL. Which approach best meets these requirements?
- A
Install and configure the Snowflake Connector for ServiceNow in ServiceNow, set up a Snowflake connection with appropriate credentials and network security, and use the connector's data extraction framework to move selected ServiceNow table data into Snowflake on a defined schedule.
- B
Use Snowpipe Streaming directly from ServiceNow business rules to push every incident update into Snowflake because the Snowflake Connector for ServiceNow does not support scheduled extraction of ServiceNow table data.
- C
Replicate the entire ServiceNow operational database into Snowflake using database-level CDC because the Snowflake Connector for ServiceNow is intended only for authentication and cannot move business data.
- D
Export ServiceNow data to CSV files on a shared file system and have Snowflake auto-ingest them with external stages, because the Snowflake Connector for ServiceNow requires file-based transfers rather than direct connectivity.
Show answer and explanation
Correct answer: A
Explanation
The best answer is Option 1 because the Snowflake Connector for ServiceNow is intended to provide a supported mechanism for extracting ServiceNow data into Snowflake without requiring architects to build and maintain bespoke ETL code. In practice, architects should focus on secure connector configuration, least-privilege credentials, network/security controls, and table/schedule design for the required analytics scope. The distractors reflect common misconceptions: that ServiceNow data must be integrated through custom streaming code, that customers can use low-level database replication against a SaaS backend, or that file-based staging is required for the connector. Snowflake and ServiceNow documentation for the connector and associated setup guidance should be used to validate supported deployment patterns, security prerequisites, and operational scheduling capabilities.
- A. Correct.
Correct. The Snowflake Connector for ServiceNow is designed to extract data from ServiceNow tables and load it into Snowflake using a supported integration pattern managed from ServiceNow. This aligns with the requirement for minimal custom development and operational ownership by ServiceNow administrators. The scenario also correctly emphasizes configuring secure connectivity, credentials, and scheduling rather than writing custom ETL pipelines.
- B. Incorrect.
Incorrect. This option describes a custom event-driven integration pattern rather than the Snowflake Connector for ServiceNow. While organizations can build custom integrations with Snowflake APIs or ingestion services, that does not match the requirement for a supported, low-code connector operated by ServiceNow administrators. The claim that the connector does not support scheduled extraction is also misleading.
- C. Incorrect.
Incorrect. ServiceNow is a SaaS application, so database-level CDC replication of its underlying operational database is not the supported pattern for customers. The Snowflake Connector for ServiceNow is specifically intended to move ServiceNow business data into Snowflake for analytics use cases, not merely to handle authentication.
- D. Incorrect.
Incorrect. File export and ingest can be a valid generic integration pattern, but it is not the defining or required architecture for the Snowflake Connector for ServiceNow. This option introduces unnecessary manual handling and infrastructure complexity, which conflicts with the requirement for minimal custom development and supported administration from ServiceNow.