Question 550A new Snowpipe definition exists but cloud object notifications never reach it. An engineer proposes to verify the external stage integration and notification channel end to end. Which explanation best describes why this is appropriate? Snowpipe runs its supported ingestion service separately from user-managed warehouse COPY runs. Auto-ingest depends on a supported event path between object storage and the pipe. Snowpipe continuously loads eligible new staged files through managed ingest compute. Snowpipe uses configured COPY logic and exposes ingestion error evidence. ExplanationCorrect Answer B:Auto-ingest depends on a supported event path between object storage and the pipe. This is testable: uploading one test object produces an observable pipe event and target rows. Incorrect Answers A:Snowpipe runs its supported ingestion service separately from user-managed warehouse COPY runs. For the current requirement, the decisive mechanism is: Auto-ingest depends on a supported event path between object storage and the pipe. The related action is: Verify the external stage integration and notification channel end to end. C:Snowpipe continuously loads eligible new staged files through managed ingest compute. For the current requirement, the decisive mechanism is: Auto-ingest depends on a supported event path between object storage and the pipe. The related action is: Verify the external stage integration and notification channel end to end. D:Snowpipe uses configured COPY logic and exposes ingestion error evidence. For the current requirement, the decisive mechanism is: Auto-ingest depends on a supported event path between object storage and the pipe. The related action is: Verify the external stage integration and notification channel end to end.
Question 551A query service stores several roles on its user but uses the same default role for all jobs. After the team decides to set an explicit primary role per job and review any secondary roles it activates, which observation most directly validates the result? An intended account role receives SELECT through its database-role grant. The new table's owner matches the explicitly selected deployment role. Query history and CURRENT_ROLE() show the expected job-specific identity. The active account role inherits the intended database privilege and queries succeed. ExplanationCorrect Answer C:Query history and CURRENT_ROLE() show the expected job-specific identity. This matters because assigned roles do not mean every session automatically has the same effective privileges. Incorrect Answers A:Database roles provide reusable database-local privilege bundles through account roles. This is not the decisive validation for the stated requirement. The relevant evidence is: Query history and CURRENT_ROLE() show the expected job-specific identity. B:New-object ownership and CREATE authorization are based on the session primary role. This is not the decisive validation for the stated requirement. The relevant evidence is: Query history and CURRENT_ROLE() show the expected job-specific identity. D:Database roles are granted within database scope and cannot themselves become session roles. This is not the decisive validation for the stated requirement. The relevant evidence is: Query history and CURRENT_ROLE() show the expected job-specific identity.
Question 552A team uses Snowpark for a simple SELECT DISTINCT that its existing SQL view already performs adequately. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Large intermediate tables spill or consume more warehouse time. Pipelines continue with incorrect data after upstream schema changes. Partial runs publish inconsistent results without a clear recovery point. Unnecessary runtime complexity increases operational maintenance. ExplanationCorrect Answer D:Unnecessary runtime complexity increases operational maintenance. The direct prevention is to compare native SQL with Snowpark code for the measured requirement before adding runtime complexity. Snowpark enables supported language processing but not every operation needs additional code. Incorrect Answers A:Early reduction of rows limits intermediate join work when optimizer and predicates allow. The immediate omission risk in this case is: Unnecessary runtime complexity increases operational maintenance. B:Source evolution can silently change downstream mappings and expectations. The immediate omission risk in this case is: Unnecessary runtime complexity increases operational maintenance. C:Task graphs provide ordered execution and per-step operational visibility. The immediate omission risk in this case is: Unnecessary runtime complexity increases operational maintenance.
Question 553An unattended service stores a human password in a plain-text scheduled job. Which Snowflake configuration or operational action most directly addresses this situation? Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. Evaluate an approved OAuth integration with least-privilege application scopes. Require appropriate MFA for eligible interactive identities under account policy. Apply a scoped network policy allowing only approved client sources. ExplanationCorrect Answer A:Service identities should authenticate without embedding reusable employee passwords. The matching action is to use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. A rotated service credential succeeds without exposing a password in job configuration. Incorrect Answers B:OAuth separates delegated authorization and token lifetimes from persistent user passwords. The operative distinction here is: Service identities should authenticate without embedding reusable employee passwords. The targeted change 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. The operative distinction here is: Service identities should authenticate without embedding reusable employee passwords. The targeted change is: Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials. D:Network access rules evaluate connection origin separately from role permissions. The operative distinction here is: Service identities should authenticate without embedding reusable employee passwords. The targeted change is: Use a supported nonhuman authentication method such as key-pair or approved OAuth credentials.
Question 554A view owner updates its SQL but an analyst still believes the view stores an old static snapshot. An engineer proposes to explain standard-view evaluation against source tables at query time. Which explanation best describes why this is appropriate? Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. Standard views evaluate their definition using current authorized data. Materialized views maintain eligible precomputed results for repeated query access. A standard view saves a query definition rather than materializing its full result table. ExplanationCorrect Answer B:Standard views evaluate their definition using current authorized data. This is testable: an approved source-row change appears through the view without a view reload step. Incorrect Answers A:Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. For the current requirement, the decisive mechanism is: Standard views evaluate their definition using current authorized data. The related action is: Explain standard-view evaluation against source tables at query time. C:Materialized views maintain eligible precomputed results for repeated query access. For the current requirement, the decisive mechanism is: Standard views evaluate their definition using current authorized data. The related action is: Explain standard-view evaluation against source tables at query time. D:A standard view saves a query definition rather than materializing its full result table. For the current requirement, the decisive mechanism is: Standard views evaluate their definition using current authorized data. The related action is: Explain standard-view evaluation against source tables at query time.
Question 555Two departments create same-named tables in different schemas and analysts run unqualified queries. After the team decides to specify the intended database and schema in the session or fully qualify the table, which observation most directly validates the result? The assigned role can select from the intended fully qualified table but no unrelated schema. The application calls the fully qualified sequence and receives generated values. A qualified query resolves to the approved department's table. The provider's share metadata lists only explicitly approved objects. ExplanationCorrect Answer C:A qualified query resolves to the approved department's table. This matters because name resolution follows the current database/schema context unless a full object name is supplied. Incorrect Answers A:Authorization to reach a table requires visibility of its enclosing namespace. This is not the decisive validation for the stated requirement. The relevant evidence is: A qualified query resolves to the approved department's table. B:Sequences are schema objects whose names resolve under the current namespace. This is not the decisive validation for the stated requirement. The relevant evidence is: A qualified query resolves to the approved department's table. D:Shares expose specifically authorized database objects to consumers rather than storing application rows. This is not the decisive validation for the stated requirement. The relevant evidence is: A qualified query resolves to the approved department's table.
Question 556A reporting team needs a virtual representation of data without storing a new full copy. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Sensitive logic or intermediate information can leak to a recipient. Analysts incorrectly blame stale materialization for an unrelated query result. Further nesting obscures the true workload bottleneck. Duplicated reporting tables diverge from updated sources. ExplanationCorrect Answer D:Duplicated reporting tables diverge from updated sources. The direct prevention is to create a standard view over the governed source objects. A standard view saves a query definition rather than materializing its full result table. Incorrect Answers A:Secure views restrict certain optimizations and metadata exposure for protected sharing patterns. The immediate omission risk in this case is: Duplicated reporting tables diverge from updated sources. B:Standard views evaluate their definition using current authorized data. The immediate omission risk in this case is: Duplicated reporting tables diverge from updated sources. C:A view is a logical SQL abstraction and excessive nesting can complicate optimization and diagnosis. The immediate omission risk in this case is: Duplicated reporting tables diverge from updated sources.
Question 557A team puts data-file-format definitions into an application spreadsheet instead of Snowflake. Which Snowflake configuration or operational action most directly addresses this situation? Create a reusable named FILE FORMAT object in the relevant schema. Create or reference the SEQUENCE object in the intended qualified schema. Grant the least-privilege USAGE path on the database and schema as well as table SELECT. Specify the intended database and schema in the session or fully qualify the table. ExplanationCorrect Answer A:File format objects centralize parsing rules used by stages and COPY commands. The matching action is to create a reusable named FILE FORMAT object in the relevant schema. Two permitted COPY operations reference the same approved format definition. Incorrect Answers B:Sequences are schema objects whose names resolve under the current namespace. The operative distinction here is: File format objects centralize parsing rules used by stages and COPY commands. The targeted change is: Create a reusable named FILE FORMAT object in the relevant schema. C:Authorization to reach a table requires visibility of its enclosing namespace. The operative distinction here is: File format objects centralize parsing rules used by stages and COPY commands. The targeted change 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. The operative distinction here is: File format objects centralize parsing rules used by stages and COPY commands. The targeted change is: Create a reusable named FILE FORMAT object in the relevant schema.
Question 558A contractor connects from a prohibited public network despite valid object grants. An engineer proposes to apply a scoped network policy allowing only approved client sources. Which explanation best describes why this is appropriate? Service identities should authenticate without embedding reusable employee passwords. Network access rules evaluate connection origin separately from role permissions. OAuth separates delegated authorization and token lifetimes from persistent user passwords. SSO centralizes identity controls under the organization's identity provider. ExplanationCorrect Answer B:Network access rules evaluate connection origin separately from role permissions. This is testable: a permitted address connects while the blocked address cannot establish a session. Incorrect Answers A:Service identities should authenticate without embedding reusable employee passwords. For the current requirement, the decisive mechanism is: Network access rules evaluate connection origin separately from role permissions. The related action is: Apply a scoped network policy allowing only approved client sources. C:OAuth separates delegated authorization and token lifetimes from persistent user passwords. For the current requirement, the decisive mechanism is: Network access rules evaluate connection origin separately from role permissions. The related action is: Apply a scoped network policy allowing only approved client sources. D:SSO centralizes identity controls under the organization's identity provider. For the current requirement, the decisive mechanism is: Network access rules evaluate connection origin separately from role permissions. The related action is: Apply a scoped network policy allowing only approved client sources.
Question 559A pipeline loads JSON strings into VARCHAR and later tries to access nested keys as VARIANT values. After the team decides to parse the JSON into a VARIANT representation before path queries, which observation most directly validates the result? A controlled three-element array produces exactly three expected output records. The sample amounts sort and aggregate numerically, with invalid inputs flagged. A sample nested field is retrieved with the expected value and type. A two-line order produces two item rows with the correct parent ID. ExplanationCorrect Answer C:A sample nested field is retrieved with the expected value and type. This matters because vARIANT preserves semi-structured types and supports documented element-path access. Incorrect Answers A:Expansion multiplies source rows by the selected collection's elements. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample nested field is retrieved with the expected value and type. B:Typed conversion clarifies semantics for numeric predicates and calculations. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample nested field is retrieved with the expected value and type. D:FLATTEN expands array or object elements to relational rows for downstream SQL. This is not the decisive validation for the stated requirement. The relevant evidence is: A sample nested field is retrieved with the expected value and type.
Question 560A service needs to continue past selected bad files while retaining an audit of rejected rows. If the responsible team does not correct this condition, which outcome is the most relevant remaining risk? Blind retries duplicate or omit transactions. Duplicate expectations lead to incorrect row-count reconciliation. Bad source records are committed without an actionable error trail. Failures are silently ignored or the entire batch stops unexpectedly. ExplanationCorrect Answer D:Failures are silently ignored or the entire batch stops unexpectedly. The direct prevention is to choose an appropriate ON_ERROR option and record rejected-file diagnostics. COPY error-handling options determine whether loading aborts, skips or continues. Incorrect Answers A:Snowflake records file-loading outcomes that can support safe reconciliation. The immediate omission risk in this case is: Failures are silently ignored or the entire batch stops unexpectedly. B:COPY tracks previously loaded files to help avoid accidental duplicate ingestion. The immediate omission risk in this case is: Failures are silently ignored or the entire batch stops unexpectedly. C:Pre-load validation surfaces parsing and column conversion problems. The immediate omission risk in this case is: Failures are silently ignored or the entire batch stops unexpectedly.