Question 450
After the approved change, engineers revisit: A partner uses an ODBC reporting connector with a role that changes silently after an administrator modifies user defaults. Which result establishes the intended state?
Explanation
Correct Answer
The connector's role context and query results remain correct after default-role changes. This validates the relevant action: Set an approved explicit connection role and test effective privileges with the scheduled client. The underlying Snowflake behavior is: Client session role configuration can override or inherit defaults and affects object access.
Incorrect Answers
The updated client establishes an authorized session and runs the same controlled query. This evidence tests a DIFFERENT situation: A BI tool connects using an outdated driver and sees unsupported authentication failures after a platform security update. The correction required in this case is: Set an approved explicit connection role and test effective privileges with the scheduled client.
The pipeline loads representative events with measured latency and manageable operational overhead. This evidence tests a DIFFERENT situation: A data app needs to ingest events from Kafka but engineers build one file per message and a new warehouse COPY for each row. The correction required in this case is: Set an approved explicit connection role and test effective privileges with the scheduled client.
A test event reaches the target through the streaming API without writing a cloud-storage file first. This evidence tests a DIFFERENT situation: A company delivers millions of individual sensor rows through an API but assumes file-based Snowpipe can ingest unstaged row payloads directly. The correction required in this case is: Set an approved explicit connection role and test effective privileges with the scheduled client.