Snowflake SnowPro Core Practice Test 35
Question 340
For an original SnowPro Core educational scenario, consider: A team attempts to activate a database role directly with USE ROLE and receives an error. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Assign the database role directly as the session's current account role.
- Check: Inspect query references, policy evaluation or access metadata and lineage edges for representative controlled activity.
- Change: Define database roles for database object permissions, then grant them to an account role users can activate.
- Check: Inspect database-role grants, parent account-role membership and a permitted SELECT using the active account role.
- Change: Configure supported federated SSO and multifactor authentication with user provisioning and offboarding controls.
Explanation
Correct Answer
C:Database roles are scoped to their database and cannot be activated directly as session primary roles; account roles can inherit them. Evidence: Inspect database-role grants, parent account-role membership and a permitted SELECT using the active account role.
D:Database roles are scoped to their database and cannot be activated directly as session primary roles; account roles can inherit them. Required intervention: Define database roles for database object permissions, then grant them to an account role users can activate.
Incorrect Answers
A:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Database roles are scoped to their database and cannot be activated directly as session primary roles; account roles can inherit them.
B:Check: Inspect query references, policy evaluation or access metadata and lineage edges for representative controlled activity. Database roles are scoped to their database and cannot be activated directly as session primary roles; account roles can inherit them.
E:Change: Configure supported federated SSO and multifactor authentication with user provisioning and offboarding controls. Database roles are scoped to their database and cannot be activated directly as session primary roles; account roles can inherit them.
Question 341
A Snowflake engineer is examining this platform situation: A data engineer who owns a table grants unreviewed access inside a regulated managed schema. A proposed shortcut is: Permit every table owner to issue data access grants in a managed access schema. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
- Permit every table owner to issue data access grants in a managed access schema.
- Configure supported federated SSO and multifactor authentication with user provisioning and offboarding controls.
- Define appropriate FUTURE grants on the intended database or schema in addition to any existing-object grants.
Explanation
Correct Answer
A:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Applied case: A data engineer who owns a table grants unreviewed access inside a regulated managed schema.
Incorrect Answers
B:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
C:Configure supported federated SSO and multifactor authentication with user provisioning and offboarding controls. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Define appropriate FUTURE grants on the intended database or schema in addition to any existing-object grants. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 342
A Snowflake implementation review finds: A data engineer who owns a table grants unreviewed access inside a regulated managed schema. The team proposes: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Query authorization can consider active primary and secondary roles, while CREATE object ownership and required creation privileges follow primary-role semantics.
- Tags carry metadata labels and can support classification and policy attachment, but merely assigning a label does not automatically encrypt or hide every value.
- Storage integrations delegate external cloud access through controlled identity relationships, reducing exposure from embedded static credentials.
- In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Explanation
Correct Answer
D:Relevant validation before approval: Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test. This principle explains the proposed technical approach, which is: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
Incorrect Answers
A:Query authorization can consider active primary and secondary roles, while CREATE object ownership and required creation privileges follow primary-role semantics. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Tags carry metadata labels and can support classification and policy attachment, but merely assigning a label does not automatically encrypt or hide every value. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
C:Storage integrations delegate external cloud access through controlled identity relationships, reducing exposure from embedded static credentials. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 343
The data platform team has not yet approved changes. Current evidence indicates: A data engineer who owns a table grants unreviewed access inside a regulated managed schema. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect query references, policy evaluation or access metadata and lineage edges for representative controlled activity.
- Inspect tags on representative new columns and policy bindings across changing schemas.
- Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test.
- Inspect effective retention parameters and attempt a safe as-of query at an approved timestamp.
Explanation
Correct Answer
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. If confirmed, the proportionate intervention is: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
Incorrect Answers
A:Inspect query references, policy evaluation or access metadata and lineage edges for representative controlled activity. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Inspect tags on representative new columns and policy bindings across changing schemas. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Inspect effective retention parameters and attempt a safe as-of query at an approved timestamp. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 344
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A data engineer who owns a table grants unreviewed access inside a regulated managed schema. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- Each principal connects using approved mechanisms without broad authentication exceptions.
- Each dataset has a documented recovery horizon consistent with actual platform support.
- Dataset sharing requires the designated governance authority instead of arbitrary table-owner discretion.
- Auditors can identify relevant usage and downstream dependencies without granting ordinary analysts privileged raw audit access.
Explanation
Correct Answer
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. The approved implementation step was: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
Incorrect Answers
A:Each principal connects using approved mechanisms without broad authentication exceptions. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Each dataset has a documented recovery horizon consistent with actual platform support. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Auditors can identify relevant usage and downstream dependencies without granting ordinary analysts privileged raw audit access. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 345
An implementation sign-off request identifies the following problem: A data engineer who owns a table grants unreviewed access inside a regulated managed schema. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Set the correct primary role and authorized secondary-role configuration, remembering that object creation ownership uses the primary role. Verify: Compare CURRENT_ROLE, CURRENT_SECONDARY_ROLES and attempted SQL with each role mode.
- Change: Apply dynamic masking policies with role-aware conditions to appropriately classified sensitive columns. Verify: Query the same protected column under authorized and limited roles and review masking-policy bindings.
- Change: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS. Verify: Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test.
- Change: Use governed object tags, supported classification methods and appropriate tag-based policy integration. Verify: Inspect tags on representative new columns and policy bindings across changing schemas.
Explanation
Correct Answer
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. The change is successful only when: Dataset sharing requires the designated governance authority instead of arbitrary table-owner discretion.
Incorrect Answers
A:Change: Set the correct primary role and authorized secondary-role configuration, remembering that object creation ownership uses the primary role. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Change: Apply dynamic masking policies with role-aware conditions to appropriately classified sensitive columns. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Change: Use governed object tags, supported classification methods and appropriate tag-based policy integration. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 346
A Snowflake engineer is examining this platform situation: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables. A proposed shortcut is: Permit every table owner to issue data access grants in a managed access schema. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
- Define database roles for database object permissions, then grant them to an account role users can activate.
- Permit every table owner to issue data access grants in a managed access schema.
- Use governed object tags, supported classification methods and appropriate tag-based policy integration.
Explanation
Correct Answer
A:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Applied case: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables.
Incorrect Answers
B:Define database roles for database object permissions, then grant them to an account role users can activate. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Use this instead: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
D:Use governed object tags, supported classification methods and appropriate tag-based policy integration. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 347
A Snowflake implementation review finds: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables. The team proposes: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
- A role inherits the privileges of roles granted to it, and users acquire permissions through their assigned active roles.
- Reading a table normally requires privileges on its containing database and schema as well as SELECT on the table; warehouse USAGE is separate.
- Identity federation centralizes authentication while Snowflake role authorization remains a separate explicit layer.
Explanation
Correct Answer
A:Relevant validation before approval: Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test. Applied case: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables.
Incorrect Answers
B:A role inherits the privileges of roles granted to it, and users acquire permissions through their assigned active roles. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
C:Reading a table normally requires privileges on its containing database and schema as well as SELECT on the table; warehouse USAGE is separate. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Identity federation centralizes authentication while Snowflake role authorization remains a separate explicit layer. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 348
The data platform team has not yet approved changes. Current evidence indicates: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Check integration grants, cloud IAM role trust, allowed prefixes and controlled stage listing.
- Create a controlled new table after configuring grants and verify permissions separately from an old table.
- Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test.
- Inspect database-role grants, parent account-role membership and a permitted SELECT using the active account role.
Explanation
Correct Answer
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Confirm afterward that: Dataset sharing requires the designated governance authority instead of arbitrary table-owner discretion.
Incorrect Answers
A:Check integration grants, cloud IAM role trust, allowed prefixes and controlled stage listing. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Create a controlled new table after configuring grants and verify permissions separately from an old table. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
D:Inspect database-role grants, parent account-role membership and a permitted SELECT using the active account role. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
Question 349
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- The role can query only approved objects with no blanket access to sibling datasets.
- Each dataset has a documented recovery horizon consistent with actual platform support.
- Dataset sharing requires the designated governance authority instead of arbitrary table-owner discretion.
- The watched warehouse raises alerts or suspends as configured without claiming to cap unrelated charges.
Explanation
Correct Answer
C:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:The role can query only approved objects with no blanket access to sibling datasets. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
B:Each dataset has a documented recovery horizon consistent with actual platform support. A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables.
D:The watched warehouse raises alerts or suspends as configured without claiming to cap unrelated charges. A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables.
Question 350
For an original SnowPro Core educational scenario, consider: A governance group wants schema-level approval of SELECT grants even when different teams own the contained tables. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test.
- Change: Define database roles for database object permissions, then grant them to an account role users can activate.
- Check: Compare effective policy assignments, actual connection methods and login tests for both human and service identities.
- Change: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
- Permit every table owner to issue data access grants in a managed access schema.
Explanation
Correct Answer
A:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Required intervention: Use a managed access schema and delegate grant decisions to the schema owner or a role with MANAGE GRANTS.
D:In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them. Evidence: Check schema type, object ownership and whether the correct role can GRANT SELECT in a controlled test.
Incorrect Answers
B:Change: Define database roles for database object permissions, then grant them to an account role users can activate. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
C:Check: Compare effective policy assignments, actual connection methods and login tests for both human and service identities. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.
E:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. In managed access schemas, individual object owners cannot independently grant privileges; schema ownership or global grant management controls them.