A Data Engineer needs to be able to create new databases and objects as required for a Proof of Concept (POC). The sandbox Snowflake account where the POC is tested does not have Role-Based Access…

Question

Options

• AORGADMIN
• CSECURITYADMIN
• DSYSADMIN

• A
  9% (3)
• C
  3% (1)
• D
  88% (28)

Explanation

SYSADMIN is the correct answer because it is the lowest-privileged system role that can create and manage databases, schemas, tables, and other objects in Snowflake - exactly what a Data Engineer needs for a POC. Since the sandbox account has no RBAC configured, there are no custom roles to fall back on, making SYSADMIN the minimal viable choice.

ORGADMIN (A) is overkill: it manages organization-level settings across all accounts in the org (billing, account creation, etc.) and has no direct object-creation authority in a single account - it's the wrong tool and far too broad. SECURITYADMIN (C) is also wrong: it manages users and grants, not database objects; granting it here would give unnecessary access to security configuration without solving the actual need.

Memory tip: Think of Snowflake's built-in role hierarchy as a ladder - ORGADMIN → ACCOUNTADMIN → SECURITYADMIN → SYSADMIN → PUBLIC. For building things (databases, schemas, objects), SYSADMIN is the lowest rung that does the job; everything above it adds administrative power you don't need.

No community discussion yet for this question.