Question 130
After the approved change, engineers revisit: A Snowflake Python Connector job reaches the wrong account because the application uses a short legacy account locator. Which result establishes the intended state?
Explanation
Correct Answer
Session metadata shows the intended target account and query history records the application job. This validates the relevant action: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context. The underlying Snowflake behavior is: Account identification and cloud region routing are connection configuration dependencies.
Incorrect Answers
The function reaches only its approved host, while an unrelated outbound request is denied. This evidence tests a DIFFERENT situation: An external UDF sends public data to an API, but the security review discovers its request uses an unrestricted outbound network rule. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.
An authorized production test object produces a corresponding pipe load-history event. This evidence tests a DIFFERENT situation: A cloud storage event notification invokes Snowpipe from a test bucket, but production bucket events point to a stale integration identifier. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.
A dry-run or test load includes only source files for the approved business feed. This evidence tests a DIFFERENT situation: A staged directory contains many unrelated feeds and COPY loads data intended for another department. The correction required in this case is: Configure the approved organization-account identifier or fully qualified account endpoint with the correct region context.