A data engineer needs to create a new database named SALES DATA for storing sales transactions. They want to ensure that only users with the 'DB_ADMIN' role can manage the database. After creating the

Question

Options

• ACREATE DATABASE SALES DATA; GRANT OWNERSHIP ON DATABASE SALES DATA TO
• BCREATE DATABASE SALES DATA; GRANT OWNERSHIP ON DATABASE SALES DATA TO
• CCREATE DATABASE SALES DATA; GRANT OWNERSHIP ON DATABASE SALES DATA TO
• DCREATE DATABASE SALES DATA; USE DATABASE SALES DATA; GRANT OWNERSHIP ON
• ECREATE DATABASE SALES DATA; GRANT OWNERSHIP ON DATABASE SALES DATA TO

• A
  4% (2)
• B
  58% (30)
• C
  10% (5)
• D
  23% (12)
• E
  6% (3)

Explanation

Note: The answer choices appear truncated in your question, so this explanation focuses on the underlying Snowflake concepts that make B correct.

Option B is correct because it follows the proper Snowflake sequence: creating the database with the name properly quoted (e.g., "SALES DATA") to handle the space, granting OWNERSHIP to ROLE DB_ADMIN using the ROLE keyword explicitly, and then using GRANT SELECT ON FUTURE TABLES IN SCHEMA "SALES DATA".PUBLIC TO ROLE ANALYST - which is the most efficient single command for a newly created schema.

• Option A likely omits quoting "SALES DATA" or uses incorrect identifier syntax, causing a parse error since unquoted identifiers cannot contain spaces.
• Option C probably grants ALL PRIVILEGES instead of just SELECT, violating the principle of least privilege and making it less secure.
• Option D inserts an unnecessary USE DATABASE statement - fully qualified object names make this redundant and add noise without benefit.
• Option E likely grants the privilege to a USER directly rather than a ROLE, bypassing Snowflake's role-based access control (RBAC) model, which is insecure and unscalable.

Memory tip: Think "ROOF" - Role (always grant to roles, not users), Ownership before privileges, Object names quoted when they contain spaces, Future tables for new schemas. If any step breaks ROOF, that answer is wrong.

No community discussion yet for this question.