An administrator needs to enable account-level features such as managing organisation account parameters, configuring account-wide replication, and viewing all billing and usage data. Which system-defined role grants the broadest authority required to perform every one of these account-level operations?
- ASYSADMIN, because owning the object-creation branch gives it the account-wide authority needed to set account parameters and configure replication
- BSECURITYADMIN, because managing users, roles, and grants extends to managing account parameters, replication settings, and viewing all account billing data
- CACCOUNTADMIN, because it sits at the top of the role hierarchy and holds the privileges needed to manage account parameters, replication, and billing Correct
- DORGADMIN, because it manages billing and replication and therefore also configures the account parameters and usage views inside each individual account
Why A is wrong: SYSADMIN manages databases, warehouses, and other objects but lacks account-level rights over parameters, replication, and billing, so it cannot cover every listed operation.
Why B is wrong: SECURITYADMIN administers identities and grants but does not control account parameters, replication, or billing, so the claim that its authority extends there is incorrect.
Why C is correct: ACCOUNTADMIN encapsulates SYSADMIN and SECURITYADMIN and adds account-level authority over parameters, replication, and billing, so it is the only role spanning all listed operations.
Why D is wrong: ORGADMIN manages organisation-level tasks like creating accounts, but it does not administer the in-account parameters and usage views described, so it does not span all the listed operations.