hardMultiple ChoiceObjective-mapped
CISSP Practice Question: Designing an access control system for a highly…
A company is designing an access control system for a highly sensitive database. They want to ensure that only authorized users can access data, and that access is automatically revoked when the user's context changes (e.g., job role change). Which model BEST meets these requirements?
⚠ Common exam trap
Watch out — candidates often choose RBAC (Option C) because it is role-based and seems to handle role changes, but they miss that RBAC typically requires manual or periodic updates to revoke access, whereas ABAC provides automatic, real-time revocation based on dynamic attribute changes.
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
✓
Attribute-based access control (ABAC) with dynamic policy evaluation.
ABAC with dynamic policy evaluation is the best fit because it uses attributes (user, resource, environment) to make real-time access decisions. This allows access to be automatically revoked when context changes, such as a job role update, without manual intervention or periodic reviews.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Attribute-based access control (ABAC) with dynamic policy evaluation.
Why this is correct
Attribute-based access control (ABAC) is the most suitable model for highly dynamic environments because it evaluates access requests against policies that consider multiple attributes of the subject (user), object (resource), action, and environment in real-time. This dynamic policy evaluation allows access decisions to adapt instantly to changing conditions, such as a user's current location, time of day, or the sensitivity of the data being accessed, providing fine-grained and context-aware authorization.
- ✗
Discretionary access control (DAC) with access control lists.
Why it's wrong here
Discretionary access control (DAC) is inappropriate for a highly dynamic system due to its reliance on individual resource owners to grant or revoke access permissions, typically managed via access control lists (ACLs). This decentralized approach lacks a centralized policy engine and makes consistent enforcement and automatic adaptation to changing security postures extremely difficult. It cannot enforce automatic revocation or respond uniformly to dynamic environmental shifts.
- ✗
Role-based access control (RBAC) with periodic reviews.
Why it's wrong here
Role-based access control (RBAC), while effective for simplifying access management by assigning permissions to roles, does not inherently support the dynamic, real-time evaluation of contextual attributes beyond a user's assigned role. Periodic reviews are a reactive measure to maintain policy alignment, not a mechanism for automatic, immediate adjustments based on evolving conditions like changes in a user's project status or the sensitivity of a specific transaction.
- ✗
Mandatory access control (MAC) with security labels.
Why it's wrong here
Mandatory access control (MAC) enforces strict, system-wide security policies based on fixed sensitivity labels assigned to subjects and objects, such as "Top Secret" or "Confidential." While providing strong security guarantees in highly classified environments, MAC is inherently static and lacks the flexibility to adapt access based on real-time, granular contextual attributes beyond these predefined classifications. It cannot dynamically adjust access based on transient conditions.
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
Asset Security: Privacy and Data Retention
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
Key term
Access control
Access control is the security practice of determining who or what is allowed to view, use, or enter a resource, and under what conditions.
About these practice questions
This CISSP question is part of Courseiva's 747-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CISSP 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 CISSP exam.