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. An analyst is granted SELECT on a sales table but still cannot query it because the database and schema are not usable by the role. Which evidence should be inspected first to isolate the likely cause?
Inspect SHOW GRANTS, active primary and secondary roles, and object hierarchy. These checks diagnose Least privilege with role grants. Correct response: Grant the minimal database and schema USAGE plus table SELECT privileges to the intended role. Expected observation: A session using that role reads the target table but cannot access unrelated tables.
Inspect object dependencies, lineage events, query history and metadata availability. Those checks would investigate Data lineage for regulated transformations, not the current Least privilege with role grants failure. The targeted diagnostic here is: Inspect SHOW GRANTS, active primary and secondary roles, and object hierarchy.
Inspect masking policy definition, column bindings, role evaluation and test queries. Those checks would investigate Dynamic column masking, not the current Least privilege with role grants failure. The targeted diagnostic here is: Inspect SHOW GRANTS, active primary and secondary roles, and object hierarchy.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Least privilege with role grants failure. The targeted diagnostic here is: Inspect SHOW GRANTS, active primary and secondary roles, and object hierarchy.
A Snowflake implementation team encounters this specific requirement: A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly. Which action best addresses it?
Grant the reader role to the reporting role following the approved account role hierarchy. This resolves Role hierarchy inheritance. Underlying reason: Roles may inherit privileges of roles granted to them, providing reusable RBAC composition. Verify with: The reporting role inherits intended reader access without gaining unrelated writer privileges. Boundary: The direction of role grants matters; inheritance does not flow both ways.
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.
Attach a correctly configured resource monitor and threshold actions to supported warehouse resources. That is suitable for a different requirement, Resource monitor credit threshold, with this separate condition: An ad hoc warehouse consumes far more credits than allocated and the team wants an automated spending guardrail.
Configure supported SAML federation and validate identity attribute mappings and login routing. That is suitable for a different requirement, Federated SSO with corporate identity, with this separate condition: A company wants employees to authenticate using its corporate identity provider instead of local passwords.
After implementing a Snowflake control, the reviewer must prove the business requirement was met. A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly. Which result is the most direct acceptance evidence?
The reporting role inherits intended reader access without gaining unrelated writer privileges. This directly demonstrates success for Role hierarchy inheritance. Implementation: Grant the reader role to the reporting role following the approved account role hierarchy. Mechanism: Roles may inherit privileges of roles granted to them, providing reusable RBAC composition.
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 Role hierarchy inheritance requirement. For the current context, verify: The reporting role inherits intended reader access without gaining unrelated writer privileges.
A test user signs in through the approved IdP and receives the intended Snowflake identity. This outcome is evidence for the separate Federated SSO with corporate identity case, not the described Role hierarchy inheritance requirement. For the current context, verify: The reporting role inherits intended reader access without gaining unrelated writer privileges.
Allowed test clients connect while a verified unapproved source address is denied. This outcome is evidence for the separate Network policy for trusted admin paths case, not the described Role hierarchy inheritance requirement. For the current context, verify: The reporting role inherits intended reader access without gaining unrelated writer privileges.
A Snowflake specialist explains why a proposed design works. A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly. Which technical principle is most relevant?
Roles may inherit privileges of roles granted to them, providing reusable RBAC composition. This explains Role hierarchy inheritance. Correct implementation: Grant the reader role to the reporting role following the approved account role hierarchy. Acceptance evidence: The reporting role inherits intended reader access without gaining unrelated writer privileges.
OAuth delegates authorization using scoped tokens subject to Snowflake role privileges. This mechanism concerns OAuth delegated application tokens. The mechanism specific to Role hierarchy inheritance is: Roles may inherit privileges of roles granted to them, providing reusable RBAC composition.
Query tags attach contextual metadata to statements without automatically changing execution behavior. This mechanism concerns Query tagging for audit trail. The mechanism specific to Role hierarchy inheritance is: Roles may inherit privileges of roles granted to them, providing reusable RBAC composition.
A managed security posture capability can identify configuration concerns beyond individual queries. This mechanism concerns Trust Center security posture findings. The mechanism specific to Role hierarchy inheritance is: Roles may inherit privileges of roles granted to them, providing reusable RBAC composition.
The project leaves the described Snowflake requirement unresolved. A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly. Which consequence is most directly related?
Duplicating grants on every team role produces entitlement drift and difficult revocation. This is the direct exposure if Role hierarchy inheritance is not handled. Recommended protection: Grant the reader role to the reporting role following the approved account role hierarchy. Validate by: The reporting role inherits intended reader access without gaining unrelated writer privileges.
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 Role hierarchy inheritance is: Duplicating grants on every team role produces entitlement drift and difficult revocation.
Separate dashboards alone do not prevent ad hoc SQL from reading other regions. This is an exposure in a separate Row-level regional access scenario. The direct failure for Role hierarchy inheritance is: Duplicating grants on every team role produces entitlement drift and difficult revocation.
Broad public ingress with weak identity controls expands the account's attack surface. This is an exposure in a separate Network policy for trusted admin paths scenario. The direct failure for Role hierarchy inheritance is: Duplicating grants on every team role produces entitlement drift and difficult revocation.
The Snowflake implementation fails its pilot test. A reporting role should inherit a narrow reader role but currently needs every SELECT privilege granted repeatedly. Which evidence should be inspected first to isolate the likely cause?
Inspect the role hierarchy, granted roles and an impersonated access test. These checks diagnose Role hierarchy inheritance. Correct response: Grant the reader role to the reporting role following the approved account role hierarchy. Expected observation: The reporting role inherits intended reader access without gaining unrelated writer privileges.
Inspect policy signature, mapping table, CURRENT_ROLE logic and test role results. Those checks would investigate Row-level regional access, not the current Role hierarchy inheritance failure. The targeted diagnostic here is: Inspect the role hierarchy, granted roles and an impersonated access test.
Inspect classification output, sample false positives, tags and consumer access tests. Those checks would investigate Sensitive data discovery before sharing, not the current Role hierarchy inheritance failure. The targeted diagnostic here is: Inspect the role hierarchy, granted roles and an impersonated access test.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Role hierarchy inheritance failure. The targeted diagnostic here is: Inspect the role hierarchy, granted roles and an impersonated access test.
A Snowflake implementation team encounters this specific requirement: Object creators in a finance schema grant confidential views to other teams without central review. Which action best addresses it?
Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. This resolves Managed access schema grants. Underlying reason: Managed access schemas centralize privilege-grant authority separately from object ownership. Verify with: Individual object creators cannot independently regrant protected objects in that managed schema. Boundary: Managed access does not automatically revoke all existing access without review.
Use supported Snowflake lineage or access-history metadata to document upstream and downstream object relationships. That is suitable for a different requirement, Data lineage for regulated transformations, with this separate condition: Auditors must trace a reported metric back through transformation objects instead of trusting a spreadsheet diagram.
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.
Apply current Snowflake-supported strong authentication and MFA policy for human identities with approved exceptions. That is suitable for a different requirement, Human MFA enforcement, with this separate condition: Human users still authenticate with only a password to a privileged Snowflake account, despite organizational MFA policy.
After implementing a Snowflake control, the reviewer must prove the business requirement was met. Object creators in a finance schema grant confidential views to other teams without central review. Which result is the most direct acceptance evidence?
Individual object creators cannot independently regrant protected objects in that managed schema. This directly demonstrates success for Managed access schema grants. Implementation: Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. Mechanism: Managed access schemas centralize privilege-grant authority separately from object ownership.
The app receives access for authorized scopes and unauthorized Snowflake objects remain protected. This outcome is evidence for the separate OAuth delegated application tokens case, not the described Managed access schema grants requirement. For the current context, verify: Individual object creators cannot independently regrant protected objects in that managed schema.
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 Managed access schema grants requirement. For the current context, verify: Individual object creators cannot independently regrant protected objects in that managed schema.
EMEA and Americas test roles receive only their intended regions from the same SELECT. This outcome is evidence for the separate Row-level regional access case, not the described Managed access schema grants requirement. For the current context, verify: Individual object creators cannot independently regrant protected objects in that managed schema.
A Snowflake specialist explains why a proposed design works. Object creators in a finance schema grant confidential views to other teams without central review. Which technical principle is most relevant?
Managed access schemas centralize privilege-grant authority separately from object ownership. This explains Managed access schema grants. Correct implementation: Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. Acceptance evidence: Individual object creators cannot independently regrant protected objects in that managed schema.
Authentication policies constrain allowed login mechanisms separately from object authorization. This mechanism concerns Human MFA enforcement. The mechanism specific to Managed access schema grants is: Managed access schemas centralize privilege-grant authority separately from object ownership.
A managed security posture capability can identify configuration concerns beyond individual queries. This mechanism concerns Trust Center security posture findings. The mechanism specific to Managed access schema grants is: Managed access schemas centralize privilege-grant authority separately from object ownership.
Resource monitors track eligible credit consumption against configured budgets and actions. This mechanism concerns Resource monitor credit threshold. The mechanism specific to Managed access schema grants is: Managed access schemas centralize privilege-grant authority separately from object ownership.
The project leaves the described Snowflake requirement unresolved. Object creators in a finance schema grant confidential views to other teams without central review. Which consequence is most directly related?
Unmanaged object grants can circumvent governance expectations even with correct tables. This is the direct exposure if Managed access schema grants is not handled. Recommended protection: Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. Validate by: Individual object creators cannot independently regrant protected objects in that managed schema.
Treating SSO as a replacement for object grants can leave broad or denied data access. This is an exposure in a separate Federated SSO with corporate identity scenario. The direct failure for Managed access schema grants is: Unmanaged object grants can circumvent governance expectations even with correct tables.
Ignoring persistent posture findings can leave vulnerable settings after application rollout. This is an exposure in a separate Trust Center security posture findings scenario. The direct failure for Managed access schema grants is: Unmanaged object grants can circumvent governance expectations even with correct tables.
A successful login record alone does not prove a sensitive table was queried. This is an exposure in a separate Login history versus access history scenario. The direct failure for Managed access schema grants is: Unmanaged object grants can circumvent governance expectations even with correct tables.
The Snowflake implementation fails its pilot test. Object creators in a finance schema grant confidential views to other teams without central review. Which evidence should be inspected first to isolate the likely cause?
Inspect schema MANAGED ACCESS status, grantor permissions and attempted unauthorized GRANT. These checks diagnose Managed access schema grants. Correct response: Use a managed access schema and delegate grant administration to the schema owner or suitable MANAGE GRANTS authority. Expected observation: Individual object creators cannot independently regrant protected objects in that managed schema.
Inspect security integration, token scopes, current role and failed unauthorized requests. Those checks would investigate OAuth delegated application tokens, not the current Managed access schema grants failure. The targeted diagnostic here is: Inspect schema MANAGED ACCESS status, grantor permissions and attempted unauthorized GRANT.
Inspect object dependencies, lineage events, query history and metadata availability. Those checks would investigate Data lineage for regulated transformations, not the current Managed access schema grants failure. The targeted diagnostic here is: Inspect schema MANAGED ACCESS status, grantor permissions and attempted unauthorized GRANT.
Compare LOGIN_HISTORY, QUERY_HISTORY, ACCESS_HISTORY and timestamps or retention bounds. Those checks would investigate Login history versus access history, not the current Managed access schema grants failure. The targeted diagnostic here is: Inspect schema MANAGED ACCESS status, grantor permissions and attempted unauthorized GRANT.
Please check your mailbox for a message from support@examlabs.com and follow the directions.