Question 340A team wants one reusable scalar calculation across several SQL reports and duplicates the expression manually. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Filters run at the wrong stage and return extra records. The report selects an arbitrary earlier order or loses important columns. Replays accumulate multiple rows for the same business key. Copied expressions diverge when tax or business rules change. ExplanationCorrect Answer D:Copied expressions diverge when tax or business rules change. The direct prevention is to implement a suitably governed UDF with reviewed input and output types. User-defined functions package reusable expressions under access control. Incorrect Answers A:QUALIFY filters results of window expressions without wrapping every query in a subquery. The immediate omission risk in this case is: Copied expressions diverge when tax or business rules change. B:A window ordering assigns ranks while preserving original row attributes. The immediate omission risk in this case is: Copied expressions diverge when tax or business rules change. C:MERGE applies conditional DML using source-target match rules in one statement. The immediate omission risk in this case is: Copied expressions diverge when tax or business rules change.
Question 341A BI query changes target schemas when an analyst opens a worksheet under another database. Which Snowflake configuration or operational action most directly addresses this situation? Set explicit database/schema context or use fully qualified references. Bind the workload to the approved warehouse explicitly in its session configuration. Initialize required session variables in each new connection before executing dependent SQL. Set and verify the session's authorized primary role before execution. ExplanationCorrect Answer A:Unqualified SQL names depend on the current session namespace. The matching action is to set explicit database/schema context or use fully qualified references. The same SQL selects the expected table with either worksheet's default context. Incorrect Answers B:Current warehouse context determines where eligible SQL statements execute. The operative distinction here is: Unqualified SQL names depend on the current session namespace. The targeted change is: Set explicit database/schema context or use fully qualified references. C:Session variables are scoped to the connection rather than durable account metadata. The operative distinction here is: Unqualified SQL names depend on the current session namespace. The targeted change is: Set explicit database/schema context or use fully qualified references. D:The current role determines object ownership on CREATE and contributes effective privileges. The operative distinction here is: Unqualified SQL names depend on the current session namespace. The targeted change is: Set explicit database/schema context or use fully qualified references.
Question 342An unattended service stores a human password in a plain-text scheduled job. An engineer proposes to use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. Which explanation best describes why this is appropriate? Network access rules evaluate connection origin separately from role permissions. Service identities should authenticate without embedding reusable employee passwords. A second authentication factor reduces risk from password-only compromise. OAuth separates delegated authorization and token lifetimes from persistent user passwords. ExplanationCorrect Answer B:Service identities should authenticate without embedding reusable employee passwords. This is testable: a rotated service credential succeeds without exposing a password in job configuration. Incorrect Answers A:Network access rules evaluate connection origin separately from role permissions. For the current requirement, the decisive mechanism is: Service identities should authenticate without embedding reusable employee passwords. The related action is: Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. C:A second authentication factor reduces risk from password-only compromise. For the current requirement, the decisive mechanism is: Service identities should authenticate without embedding reusable employee passwords. The related action is: Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. D:OAuth separates delegated authorization and token lifetimes from persistent user passwords. For the current requirement, the decisive mechanism is: Service identities should authenticate without embedding reusable employee passwords. The related action is: Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials.
Question 343A pipeline receives thousands of tiny files and credits rise while ingestion overhead dominates. After the team decides to batch events into suitably sized files and review supported ingestion throughput guidance, which observation most directly validates the result? New test files appear in the table within the documented operational target. Uploading one test object produces an observable pipe event and target rows. Average input file size improves and credit-adjusted ingestion stabilizes. The corrected test file loads successfully with its prior error resolved. ExplanationCorrect Answer C:Average input file size improves and credit-adjusted ingestion stabilizes. This matters because too many very small files impose disproportionate ingestion and metadata overhead. Incorrect Answers A:Snowpipe continuously loads eligible new staged files through managed ingest compute. This is not the decisive validation for the stated requirement. The relevant evidence is: Average input file size improves and credit-adjusted ingestion stabilizes. B:Auto-ingest depends on a supported event path between object storage and the pipe. This is not the decisive validation for the stated requirement. The relevant evidence is: Average input file size improves and credit-adjusted ingestion stabilizes. D:Snowpipe uses configured COPY logic and exposes ingestion error evidence. This is not the decisive validation for the stated requirement. The relevant evidence is: Average input file size improves and credit-adjusted ingestion stabilizes.
Question 344A Kafka topic carries order events but the integration developer plans a once-per-month CSV export. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Local SQL copies drift from reviewed source history. Secrets leak and the external call bypasses approved network controls. A compromised integration has unnecessarily broad data exposure. Order insights are delayed by an inappropriate batch export schedule. ExplanationCorrect Answer D:Order insights are delayed by an inappropriate batch export schedule. The direct prevention is to evaluate a supported Snowflake Kafka ingestion connector aligned with freshness requirements. Managed Kafka integration supports event-driven delivery without manual monthly file creation. Incorrect Answers A:Git integration connects version-controlled code assets to authorized Snowflake workflows. The immediate omission risk in this case is: Order insights are delayed by an inappropriate batch export schedule. B:API integrations govern eligible external endpoints and execution authorization. The immediate omission risk in this case is: Order insights are delayed by an inappropriate batch export schedule. C:Storage integrations couple Snowflake permissions to cloud IAM policies and approved resource paths. The immediate omission risk in this case is: Order insights are delayed by an inappropriate batch export schedule.
Question 345A developer expects a user's private stage to be visible as the table stage for a different table owner. Which Snowflake configuration or operational action most directly addresses this situation? Choose the correct user, table or named stage type for the intended ownership boundary. Stage the local file using a supported internal stage before executing COPY INTO. Create an authorized named internal stage accessible to the approved loaders. Define a suitable CSV FILE FORMAT with the correct delimiter and enclosure settings. ExplanationCorrect Answer A:Internal stage types have different visibility and ownership semantics. The matching action is to choose the correct user, table or named stage type for the intended ownership boundary. The permitted loader can list and copy the files from its intended stage. Incorrect Answers B:Bulk loading from local files uses a Snowflake-managed stage to make the source accessible. The operative distinction here is: Internal stage types have different visibility and ownership semantics. The targeted change is: Choose the correct user, table or named stage type for the intended ownership boundary. C:A named stage is a reusable schema object rather than a user-only scratch location. The operative distinction here is: Internal stage types have different visibility and ownership semantics. The targeted change is: Choose the correct user, table or named stage type for the intended ownership boundary. D:A file format controls how COPY parses delimiters, quotes and other source conventions. The operative distinction here is: Internal stage types have different visibility and ownership semantics. The targeted change is: Choose the correct user, table or named stage type for the intended ownership boundary.
Question 346A team puts data-file-format definitions into an application spreadsheet instead of Snowflake. An engineer proposes to create a reusable named FILE FORMAT object in the relevant schema. Which explanation best describes why this is appropriate? Sequences are schema objects whose names resolve under the current namespace. File format objects centralize parsing rules used by stages and COPY commands. Authorization to reach a table requires visibility of its enclosing namespace. Name resolution follows the current database/schema context unless a full object name is supplied. ExplanationCorrect Answer B:File format objects centralize parsing rules used by stages and COPY commands. This is testable: two permitted COPY operations reference the same approved format definition. Incorrect Answers A:Sequences are schema objects whose names resolve under the current namespace. For the current requirement, the decisive mechanism is: File format objects centralize parsing rules used by stages and COPY commands. The related action is: Create a reusable named FILE FORMAT object in the relevant schema. C:Authorization to reach a table requires visibility of its enclosing namespace. For the current requirement, the decisive mechanism is: File format objects centralize parsing rules used by stages and COPY commands. The related action is: Create a reusable named FILE FORMAT object in the relevant schema. D:Name resolution follows the current database/schema context unless a full object name is supplied. For the current requirement, the decisive mechanism is: File format objects centralize parsing rules used by stages and COPY commands. The related action is: Create a reusable named FILE FORMAT object in the relevant schema.
Question 347An emergency script runs daily business reports with ACCOUNTADMIN because it has every privilege. After the team decides to replace routine use with a custom reporting role limited to required tables and warehouses, which observation most directly validates the result? A low-privilege test user cannot query restricted tables through PUBLIC. A scoped operator can view approved organization-account metadata but not tenant rows. Scheduled reports succeed using only the approved reporting role. The designated operator creates a test user but cannot resize production warehouses. ExplanationCorrect Answer C:Scheduled reports succeed using only the approved reporting role. This matters because aCCOUNTADMIN is a powerful administrative role and should not be an application default. Incorrect Answers A:Every Snowflake user inherits the PUBLIC role by design. This is not the decisive validation for the stated requirement. The relevant evidence is: Scheduled reports succeed using only the approved reporting role. B:Organization scope and one account's administrative scope are distinct security boundaries. This is not the decisive validation for the stated requirement. The relevant evidence is: Scheduled reports succeed using only the approved reporting role. D:Creating principals is different from modifying compute or data objects. This is not the decisive validation for the stated requirement. The relevant evidence is: Scheduled reports succeed using only the approved reporting role.
Question 348An analyst needs interactive Query History and a visual Query Profile but only receives raw output from a custom script. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Unreviewed local edits cannot be traced to the production run. Credentials leak through version-controlled files or unsupported editor scripts. A homegrown connection layer lacks supported authentication and driver behavior. Performance triage proceeds without the relevant visual execution evidence. ExplanationCorrect Answer D:Performance triage proceeds without the relevant visual execution evidence. The direct prevention is to use Snowsight Query History and its query-detail profiling views. Snowsight presents interactive execution and activity evidence for eligible queries. Incorrect Answers A:Versioned deployment makes changes traceable and repeatable across environments. The immediate omission risk in this case is: Performance triage proceeds without the relevant visual execution evidence. B:IDE tools can combine local authoring with Snowflake execution while authentication remains controlled. The immediate omission risk in this case is: Performance triage proceeds without the relevant visual execution evidence. C:The JDBC interface integrates Java applications with Snowflake's SQL protocol. The immediate omission risk in this case is: Performance triage proceeds without the relevant visual execution evidence.
Question 349A release pipeline records neither SQL errors nor the identities that changed security-related objects. Which Snowflake configuration or operational action most directly addresses this situation? Enable and inspect appropriate access, query and operational history for audit needs. Configure a supported Snowflake alert or monitoring workflow for the evaluated condition. Review supported key management options and edition-specific requirements with security owners. Review the Snowflake Trust Center findings and enabled scanner coverage. ExplanationCorrect Answer A:Account audit records connect changes and execution to actors and timestamps. The matching action is to enable and inspect appropriate access, query and operational history for audit needs. A controlled role change is visible with a documented principal and time. Incorrect Answers B:Alerts can evaluate scheduled conditions and trigger authorized notification actions. The operative distinction here is: Account audit records connect changes and execution to actors and timestamps. The targeted change is: Enable and inspect appropriate access, query and operational history for audit needs. C:Key management choices interact with account architecture and required assurances. The operative distinction here is: Account audit records connect changes and execution to actors and timestamps. The targeted change is: Enable and inspect appropriate access, query and operational history for audit needs. D:Trust Center surfaces supported posture and risk findings in the account context. The operative distinction here is: Account audit records connect changes and execution to actors and timestamps. The targeted change is: Enable and inspect appropriate access, query and operational history for audit needs.
Question 350An engineer sees high queueing on a warehouse and enables Query Acceleration Service without considering concurrency. An engineer proposes to investigate multi-cluster scale-out for queue-bound queries before adding acceleration. Which explanation best describes why this is appropriate? Query Acceleration Service can offload eligible portions of a query to additional compute. Query acceleration targets eligible execution work, not warehouse admission contention. Search optimization maintains an access path useful for eligible high-selectivity lookups. Search optimization is not a general replacement for full-table scan processing. ExplanationCorrect Answer B:Query acceleration targets eligible execution work, not warehouse admission contention. This is testable: peak queuing declines after appropriate scaling under controlled parallel requests. Incorrect Answers A:Query Acceleration Service can offload eligible portions of a query to additional compute. For the current requirement, the decisive mechanism is: Query acceleration targets eligible execution work, not warehouse admission contention. The related action is: Investigate multi-cluster scale-out for queue-bound queries before adding acceleration. C:Search optimization maintains an access path useful for eligible high-selectivity lookups. For the current requirement, the decisive mechanism is: Query acceleration targets eligible execution work, not warehouse admission contention. The related action is: Investigate multi-cluster scale-out for queue-bound queries before adding acceleration. D:Search optimization is not a general replacement for full-table scan processing. For the current requirement, the decisive mechanism is: Query acceleration targets eligible execution work, not warehouse admission contention. The related action is: Investigate multi-cluster scale-out for queue-bound queries before adding acceleration.