212-82 · Question #115
ProNet, a leading technology firm, has been dynamically evolving its internal infrastructure to cater to an expanding workforce and changing business needs. The company's current project involves…
The correct answer is C. Role-Based Access Control (RBAC). Role-Based Access Control (RBAC) is the ideal fit because it assigns permissions to roles (e.g., Manager, Developer, HR) rather than to individual users, and users inherit permissions simply by being assigned a role - directly matching ProNet's goal of reducing administrative…
Question
ProNet, a leading technology firm, has been dynamically evolving its internal infrastructure to cater to an expanding workforce and changing business needs. The company's current project involves enhancing the overall security of its internal platforms. The company's security team is focusing on a robust access control system. To make the system efficient, it needs to implement a model that would define access based on roles within the organization, where specific roles would have predefined access to certain resources, and the roles can be assigned to multiple users. The aim is to decrease the administrative work involved in assigning permissions and ensure that users gain only the necessary permissions in line with their job functions. Which access control model best suits ProNet's requirement?
Options
- AAttribute-Based Access Control (ABAC)
- BDiscretionary Access Control (DAC)
- CRole-Based Access Control (RBAC)
- DMandatory Access Control (MAC)
How the community answered
(30 responses)- A13% (4)
- B10% (3)
- C73% (22)
- D3% (1)
Explanation
Role-Based Access Control (RBAC) is the ideal fit because it assigns permissions to roles (e.g., Manager, Developer, HR) rather than to individual users, and users inherit permissions simply by being assigned a role - directly matching ProNet's goal of reducing administrative overhead and enforcing least privilege based on job function. ABAC (A) is incorrect because it grants access based on multiple dynamic attributes (user location, time, device, etc.), making it more complex than what ProNet needs - they want straightforward role-defined access, not attribute-driven policies. DAC (B) is wrong because it allows resource owners to decide who gets access at their own discretion, which increases administrative burden and lacks centralized, role-based consistency. MAC (D) is eliminated because it relies on rigid, system-enforced security labels and classifications (common in government/military environments), which doesn't align with the flexible, role-driven structure ProNet is building.
Memory Tip: Think RBAC = Roles Before Access Checking - if the question mentions roles, job functions, reduced admin work, or permissions tied to positions, RBAC is almost always the answer. When you see labels/classifications → MAC; owner controls → DAC; multiple dynamic conditions → ABAC.
Topics
Community Discussion
No community discussion yet for this question.