Home › Certifications › Snowflake SnowPro Core › Account Management, Security and Access Control
32 multiple-choice questions and 12 flashcards on Account Management, Security and Access Control, about 11% of the Snowflake SnowPro Core bank. Every one carries a written rationale.
Account Management, Security and Access Control is one of 9 chapters in CoStudy's Snowflake SnowPro Core bank, and it holds 32 of the bank's 301 multiple-choice questions — roughly 11% of the total. That proportion is not arbitrary: chapters follow the certifying body's published exam outline, and the number of questions in each is set by that domain's published weight, so the share of your practice time this chapter takes matches the share of the real exam it accounts for.
Studying by chapter is worth doing once you have a diagnostic score. A single overall percentage tells you whether you are close; it does not tell you which domain is dragging. Working a weak chapter in isolation, and re-testing it in isolation, is the fastest way to move a score that has stalled — and it is why the mock exams in CoStudy report by domain rather than as one number.
2 questions drawn from this chapter, with the full rationale shown — the controlling principle behind the right answer, and why each wrong option tempts and fails.
Best Snowflake role to create users + manage role hierarchies?
Answer: C — SECURITYADMIN, which manages users, roles and grants
C) Correct — SECURITYADMIN inherits USERADMIN and adds global privilege management, so it can create users and roles and administer the hierarchy. A) SYSADMIN manages objects. B) USERADMIN cannot manage grants broadly. D) ACCOUNTADMIN is too broad for daily RBAC work.
A team creates custom roles for each department. To follow Snowflake's recommended hierarchy, those custom roles should ultimately be granted to:
Answer: C — SYSADMIN, so it retains visibility into objects the custom roles own
C) Correct — the recommended pattern roots custom roles under SYSADMIN so that role keeps the ability to manage objects those roles create. A) is a common mistake that concentrates object access in the account's most privileged role. B) would hand every privilege to every user, since PUBLIC is granted to all. D) confuses who administers grants with where custom roles belong in the hierarchy.
3 cards from the 12 in this chapter.
How is multi-factor authentication handled in Snowflake, and which accounts should always have it?
MFA is a built-in capability provided through the Snowflake service and enrolled per user. Every user with ACCOUNTADMIN, and generally all human interactive users, should be enrolled; service accounts should instead use key-pair or OAuth authentication rather than passwords.
Role-based access control (RBAC)?
Roles grant privileges. Users assume roles. SECURITYADMIN, USERADMIN, SYSADMIN, ACCOUNTADMIN are system roles.
Cost optimization tactics?
Right-size warehouses, shorter auto-suspend, use materialized views/result cache, separate workloads to warehouses, transient tables for staging.
These are a sample. The full Account Management, Security and Access Control chapter runs 44 items with per-chapter progress tracking, on the web and in the iOS app.
Open Snowflake SnowPro Core in CoStudy →