You save $69.98
SnowPro Core Premium Bundle
- Premium File 703 Questions & Answers
- Last Update: Nov 22, 2026
- Training Course 92 Lectures
- Study Guide 413 Pages
You save $69.98
The Snowflake implementation fails its pilot test. A company wants employees to authenticate using its corporate identity provider instead of local passwords. Which evidence should be inspected first to isolate the likely cause?
Inspect SAML integration metadata, identity claims, login history and role mapping. These checks diagnose Federated SSO with corporate identity. Correct response: Configure supported SAML federation and validate identity attribute mappings and login routing. Expected observation: A test user signs in through the approved IdP and receives the intended Snowflake identity.
Inspect object dependencies, lineage events, query history and metadata availability. Those checks would investigate Data lineage for regulated transformations, not the current Federated SSO with corporate identity failure. The targeted diagnostic here is: Inspect SAML integration metadata, identity claims, login history and role mapping.
Inspect applied tags, policy references, role evaluation and an untagged control field. Those checks would investigate Tag-driven classification and masking, not the current Federated SSO with corporate identity failure. The targeted diagnostic here is: Inspect SAML integration metadata, identity claims, login history and role mapping.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Federated SSO with corporate identity failure. The targeted diagnostic here is: Inspect SAML integration metadata, identity claims, login history and role mapping.
A Snowflake implementation team encounters this specific requirement: An organization wants sensitive administrative logins to originate only from its approved corporate egress addresses. Which action best addresses it?
Apply an appropriately scoped network policy at the supported account or user level. This resolves Network policy for trusted admin paths. Underlying reason: Network policies constrain login network sources but do not grant data privileges. Verify with: Allowed test clients connect while a verified unapproved source address is denied. Boundary: Proxy or private connectivity may affect which source IP Snowflake evaluates.
Attach a context-aware masking policy to the sensitive column using supported role conditions. That is suitable for a different requirement, Dynamic column masking, with this separate condition: Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved.
Transfer OWNERSHIP through the supported grant process with a deliberate plan for dependent privileges. That is suitable for a different requirement, Object ownership transfer, with this separate condition: A departed engineer's role owns production tables and a new maintenance role cannot perform approved ALTER operations.
Correlate login-history evidence with applicable query and access-history views rather than substituting one for another. That is suitable for a different requirement, Login history versus access history, with this separate condition: Incident responders need to distinguish whether a suspicious identity logged in from a new address versus which tables it later read.
After implementing a Snowflake control, the reviewer must prove the business requirement was met. An organization wants sensitive administrative logins to originate only from its approved corporate egress addresses. Which result is the most direct acceptance evidence?
Allowed test clients connect while a verified unapproved source address is denied. This directly demonstrates success for Network policy for trusted admin paths. Implementation: Apply an appropriately scoped network policy at the supported account or user level. Mechanism: Network policies constrain login network sources but do not grant data privileges.
A controlled report shows traceable dependencies from source tables to derived reporting objects. This outcome is evidence for the separate Data lineage for regulated transformations case, not the described Network policy for trusted admin paths requirement. For the current context, verify: Allowed test clients connect while a verified unapproved source address is denied.
A correctly tagged sensitive field receives the intended masking behavior without manual per-table policy duplication. This outcome is evidence for the separate Tag-driven classification and masking case, not the described Network policy for trusted admin paths requirement. For the current context, verify: Allowed test clients connect while a verified unapproved source address is denied.
The review finds protected columns and the shared projection excludes or masks disallowed data. This outcome is evidence for the separate Sensitive data discovery before sharing case, not the described Network policy for trusted admin paths requirement. For the current context, verify: Allowed test clients connect while a verified unapproved source address is denied.
A Snowflake specialist explains why a proposed design works. An organization wants sensitive administrative logins to originate only from its approved corporate egress addresses. Which technical principle is most relevant?
Network policies constrain login network sources but do not grant data privileges. This explains Network policy for trusted admin paths. Correct implementation: Apply an appropriately scoped network policy at the supported account or user level. Acceptance evidence: Allowed test clients connect while a verified unapproved source address is denied.
Future grants automate privileges for qualifying objects created after the grant is established. This mechanism concerns Future grants for new tables. The mechanism specific to Network policy for trusted admin paths is: Network policies constrain login network sources but do not grant data privileges.
Snowflake access checks applicable privileges on the object and its containing namespaces. This mechanism concerns Least privilege with role grants. The mechanism specific to Network policy for trusted admin paths is: Network policies constrain login network sources but do not grant data privileges.
Tags can carry semantic classification and participate in supported governance policy assignment. This mechanism concerns Tag-driven classification and masking. The mechanism specific to Network policy for trusted admin paths is: Network policies constrain login network sources but do not grant data privileges.
The project leaves the described Snowflake requirement unresolved. An organization wants sensitive administrative logins to originate only from its approved corporate egress addresses. Which consequence is most directly related?
Broad public ingress with weak identity controls expands the account's attack surface. This is the direct exposure if Network policy for trusted admin paths is not handled. Recommended protection: Apply an appropriately scoped network policy at the supported account or user level. Validate by: Allowed test clients connect while a verified unapproved source address is denied.
Applying broad future grants at account scope can unintentionally expose new sensitive datasets. This is an exposure in a separate Future grants for new tables scenario. The direct failure for Network policy for trusted admin paths is: Broad public ingress with weak identity controls expands the account's attack surface.
Undocumented transformations can hide incorrect data sources or unauthorized downstream usage. This is an exposure in a separate Data lineage for regulated transformations scenario. The direct failure for Network policy for trusted admin paths is: Broad public ingress with weak identity controls expands the account's attack surface.
Unattributed queries hinder cost and incident investigation despite complete query logs. This is an exposure in a separate Query tagging for audit trail scenario. The direct failure for Network policy for trusted admin paths is: Broad public ingress with weak identity controls expands the account's attack surface.
The Snowflake implementation fails its pilot test. An organization wants sensitive administrative logins to originate only from its approved corporate egress addresses. Which evidence should be inspected first to isolate the likely cause?
Inspect policy attachment, allowed and blocked rules, login history and effective client IP. These checks diagnose Network policy for trusted admin paths. Correct response: Apply an appropriately scoped network policy at the supported account or user level. Expected observation: Allowed test clients connect while a verified unapproved source address is denied.
Inspect object dependencies, lineage events, query history and metadata availability. Those checks would investigate Data lineage for regulated transformations, not the current Network policy for trusted admin paths failure. The targeted diagnostic here is: Inspect policy attachment, allowed and blocked rules, login history and effective client IP.
Inspect session parameters, QUERY_HISTORY, connection setup and tag values. Those checks would investigate Query tagging for audit trail, not the current Network policy for trusted admin paths failure. The targeted diagnostic here is: Inspect policy attachment, allowed and blocked rules, login history and effective client IP.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Network policy for trusted admin paths failure. The targeted diagnostic here is: Inspect policy attachment, allowed and blocked rules, login history and effective client IP.
A Snowflake implementation team encounters this specific requirement: A web analytics service needs scoped delegated access without handling employees' primary passwords. Which action best addresses it?
Configure supported OAuth security integration and application role mapping with carefully scoped tokens. This resolves OAuth delegated application tokens. Underlying reason: OAuth delegates authorization using scoped tokens subject to Snowflake role privileges. Verify with: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected. Boundary: Issuer settings and token handling must align with trusted clients and policy.
Attach an authorized row access policy using region and role-to-region mapping. That is suitable for a different requirement, Row-level regional access, with this separate condition: Managers in EMEA must see only EMEA customer records from a shared sales table even though all use the same dashboard.
Attach a context-aware masking policy to the sensitive column using supported role conditions. That is suitable for a different requirement, Dynamic column masking, with this separate condition: Support engineers can troubleshoot transactions but should see redacted account numbers unless specifically approved.
Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. That is suitable for a different requirement, Managed access schema grants, with this separate condition: Object creators in a finance schema grant confidential views to other teams without central review.
After implementing a Snowflake control, the reviewer must prove the business requirement was met. A web analytics service needs scoped delegated access without handling employees' primary passwords. Which result is the most direct acceptance evidence?
The app receives access for authorized scopes and unauthorized Snowflake objects remain protected. This directly demonstrates success for OAuth delegated application tokens. Implementation: Configure supported OAuth security integration and application role mapping with carefully scoped tokens. Mechanism: OAuth delegates authorization using scoped tokens subject to Snowflake role privileges.
The incident timeline separately identifies authentication and subsequent object-access events. This outcome is evidence for the separate Login history versus access history case, not the described OAuth delegated application tokens requirement. For the current context, verify: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
The reporting role inherits intended reader access without gaining unrelated writer privileges. This outcome is evidence for the separate Role hierarchy inheritance case, not the described OAuth delegated application tokens requirement. For the current context, verify: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
A newly created eligible table becomes readable under the approved role without manual repeat grants. This outcome is evidence for the separate Future grants for new tables case, not the described OAuth delegated application tokens requirement. For the current context, verify: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
A Snowflake specialist explains why a proposed design works. A web analytics service needs scoped delegated access without handling employees' primary passwords. Which technical principle is most relevant?
OAuth delegates authorization using scoped tokens subject to Snowflake role privileges. This explains OAuth delegated application tokens. Correct implementation: Configure supported OAuth security integration and application role mapping with carefully scoped tokens. Acceptance evidence: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
Database roles group privileges scoped to a database and are assigned through account-role inheritance paths. This mechanism concerns Database role boundaries. The mechanism specific to OAuth delegated application tokens is: OAuth delegates authorization using scoped tokens subject to Snowflake role privileges.
Future grants automate privileges for qualifying objects created after the grant is established. This mechanism concerns Future grants for new tables. The mechanism specific to OAuth delegated application tokens is: OAuth delegates authorization using scoped tokens subject to Snowflake role privileges.
Row access policies filter visible rows based on policy logic and evaluation context. This mechanism concerns Row-level regional access. The mechanism specific to OAuth delegated application tokens is: OAuth delegates authorization using scoped tokens subject to Snowflake role privileges.
The project leaves the described Snowflake requirement unresolved. A web analytics service needs scoped delegated access without handling employees' primary passwords. Which consequence is most directly related?
Copying long-lived human credentials into an app bypasses token lifecycle controls. This is the direct exposure if OAuth delegated application tokens is not handled. Recommended protection: Configure supported OAuth security integration and application role mapping with carefully scoped tokens. Validate by: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
Undocumented transformations can hide incorrect data sources or unauthorized downstream usage. This is an exposure in a separate Data lineage for regulated transformations scenario. The direct failure for OAuth delegated application tokens is: Copying long-lived human credentials into an app bypasses token lifecycle controls.
Ungoverned tags may create false confidence that sensitive columns are protected automatically. This is an exposure in a separate Tag-driven classification and masking scenario. The direct failure for OAuth delegated application tokens is: Copying long-lived human credentials into an app bypasses token lifecycle controls.
Granting table SELECT without column protection can disclose sensitive financial identifiers. This is an exposure in a separate Dynamic column masking scenario. The direct failure for OAuth delegated application tokens is: Copying long-lived human credentials into an app bypasses token lifecycle controls.
The Snowflake implementation fails its pilot test. A web analytics service needs scoped delegated access without handling employees' primary passwords. Which evidence should be inspected first to isolate the likely cause?
Inspect security integration, token scopes, current role and failed unauthorized requests. These checks diagnose OAuth delegated application tokens. Correct response: Configure supported OAuth security integration and application role mapping with carefully scoped tokens. Expected observation: The app receives access for authorized scopes and unauthorized Snowflake objects remain protected.
Inspect SHOW DATABASE ROLES, database grants and role inheritance results. Those checks would investigate Database role boundaries, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.
Inspect the role hierarchy, granted roles and an impersonated access test. Those checks would investigate Role hierarchy inheritance, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current OAuth delegated application tokens failure. The targeted diagnostic here is: Inspect security integration, token scopes, current role and failed unauthorized requests.
Please check your mailbox for a message from support@examlabs.com and follow the directions.