Design Account and Role Architecture ARA-C01 Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A financial services company operates separate Snowflake accounts for its production and development environments. The development team needs read-only access to a curated production table to build and test new data pipelines. The security team mandates that no credentials be shared between accounts and that the development account never receives write privileges on production data. What should the architect configure?

   • ACreate a custom role in the production account, grant it SELECT on the table, and grant that role to the development account's account-level admin role.
   • BCreate a share in the production account, grant SELECT on the table to the share, and add the development account as a consumer using a database role.
   • CCreate a database in the production account, grant SELECT on the table to a custom role, and share the database via a reader account.
   • DCreate a storage integration in the development account and use it to read the production table via an external stage.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A small analytics team of five users needs to create and manage its own worksheets, warehouses, and databases within a single Snowflake account. The team should not have access to any other databases in the account. The organization wants to minimize the number of custom roles to maintain. What should the architect do?

   • ACreate one custom role with CREATE DATABASE, CREATE WAREHOUSE, and CREATE SCHEMA privileges, and grant it to all five users.
   • BGrant each user the SYSADMIN role so they can create and manage their own objects.
   • CGrant each user the ACCOUNTADMIN role so they can create and manage objects and access everything.
   • DCreate a separate custom role for each user, each with CREATE DATABASE and CREATE WAREHOUSE privileges, and grant each role to its respective user.
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   What is the primary benefit of using role inheritance in Snowflake?

   • AIt simplifies privilege management by allowing child roles to inherit privileges from parent roles.
   • BIt eliminates the need for object-level privileges.
   • CIt reduces the number of users that need to be created.
   • DIt ensures that all users have the same level of access.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   A company is designing its Snowflake account and role hierarchy. They want to align the structure with their organizational departments and ensure that each department's data access is managed independently. Which approach best supports this requirement?

   • ADesign a hierarchy of accounts and roles that mirrors the organizational structure, with roles inheriting privileges from parent roles as needed.
   • BUse a single role for all users and grant it all privileges to simplify management.
   • CCreate a single account with a flat list of roles, one per department, and grant all roles the same privileges.
   • DCreate a separate account for each department and grant each account's roles access to all other accounts' data.
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   What is a key consideration in the lifecycle management of roles in Snowflake?

   • ARoles should be deleted immediately after a user leaves the organization.
   • BRoles should be kept indefinitely to avoid re-creating them later.
   • CRoles should be deactivated when they are no longer needed to reduce security risk.
   • DRoles should be modified frequently to accommodate temporary needs.
   Reveal Solution Discussion Select an answer first