mediumMultiple Choice
Role-Based Access Control: Least Privilege for Database Administrators
An organization wants to implement the principle of least privilege for its database administrators. Which approach best achieves this goal?
Quick Answer
The correct approach is to use role-based access control (RBAC) to grant permissions specific to each database administrator’s duties. RBAC directly enforces the principle of least privilege by mapping job functions—such as backup admin or security admin—to precisely defined sets of permissions, ensuring no user receives unnecessary access. On the ISC2 Certified in Cybersecurity CC exam, this concept tests your understanding of access control models; a common trap is confusing RBAC with mandatory access control (MAC), which relies on data classification labels rather than job roles. Remember that RBAC is role-centric, not label-centric. A useful memory tip: think “RBAC = Roles Before Access”—if the role doesn’t need it, the permission isn’t granted.
⚠ Common exam trap
ISC2 often tests the distinction between MAC (which controls access based on data labels) and RBAC (which controls access based on job roles), and the trap here is that candidates mistakenly choose MAC because they associate 'least privilege' with strict classification systems, not realizing that RBAC is the practical, role-specific mechanism for limiting database administrator permissions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use role-based access control (RBAC) to grant permissions specific to each administrator's duties.
Role-based access control (RBAC) directly enforces the principle of least privilege by granting database administrators only the permissions required for their specific job functions. Unlike MAC, which focuses on data classification labels, RBAC maps roles (e.g., backup admin, security admin) to precise sets of privileges, ensuring no user has unnecessary access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Implement mandatory access control (MAC) with labels for all data.
Why it's wrong here
MAC labels every data object and enforces access by clearance, which is far broader than the goal of limiting database administrators to the specific rights their role requires. It is tempting because MAC is genuinely strong for classified, need-to-know environments, but least privilege here needs role-scoped, just-enough entitlements.
- ✓
Use role-based access control (RBAC) to grant permissions specific to each administrator's duties.
Why this is correct
RBAC maps permissions to defined job roles rather than individuals, so each database administrator receives only the privileges their duties require. This enforces least privilege at scale and simplifies revocation when duties change, unlike broad shared accounts or standing administrative rights.
- ✗
Allow administrators to self-assign permissions as needed.
Why it's wrong here
Self-assigned permissions let administrators grant themselves whatever they need, directly contradicting least privilege, which requires approval-driven, minimal, time-bound entitlements. It is tempting as it reduces ticket friction, and self-service works for low-risk, non-privileged resources, but never for database administrator rights.
- ✗
Assign each administrator full database admin rights for simplicity.
Why it's wrong here
Granting every administrator full database rights gives each far more access than their duties require, the opposite of least privilege, and removes accountability boundaries. It is tempting because uniform rights reduce access tickets, and full rights suit small teams with no separation of duties, but not an organisation deliberately minimising privilege.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Access Control Fundamentals
Key term
Organization
An Organization is a top-level container in Google Cloud that represents your company or entities and serves as the root node for all your cloud resources, policies, and access control.
Key term
User
A user is any person, system, or device that interacts with an IT service, resource, or identity system, typically authenticated through credentials and authorized to perform specific actions.
About these practice questions
One of 989 original CC practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on CC
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. After a security audit, a company discovers that several employees have access to financial systems that are not required for their job roles. Which access control model would best prevent this issue in the future?
medium- A.Mandatory access control (MAC)
- B.Discretionary access control (DAC)
- ✓ C.Role-based access control (RBAC)
- D.Attribute-based access control (ABAC)
Why C: RBAC assigns permissions to roles rather than individuals, so access is granted only when a user's job role requires it. This directly enforces least privilege and prevents the audit finding where employees held unnecessary financial-system access. When roles are defined from job functions and reviewed periodically, orphaned or excessive entitlements are far easier to detect and remove.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CC practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CC exam.