What is a key benefit of using role-based access control (RBAC) in an ECS cluster?

Question

Options

• AIt simplifies management by using a single administrative account
• BIt allows unrestricted access to data for easier collaboration
• CIt enhances security by assigning permissions based on roles
• DIt requires less storage space than individual user accounts

• B
  5% (1)
• C
  90% (18)
• D
  5% (1)

Explanation

Role-based access control (RBAC) enhances security by grouping permissions into roles (e.g., "developer," "read-only," "admin") and assigning those roles to users or services - meaning no one gets more access than their job requires, a principle called least privilege. Option A is wrong because a single admin account is actually a security anti-pattern - it creates a single point of compromise and makes auditing impossible. Option B contradicts the entire purpose of access control; unrestricted access is the opposite of what RBAC provides. Option D is a red herring - RBAC is about security policy, not storage efficiency; the overhead difference is negligible and irrelevant to its purpose.

Memory tip: Think of RBAC like a hotel key card system - housekeeping cards open cleaning closets, guests open their own room, and managers open everything. Each role gets exactly the doors it needs, nothing more.

No community discussion yet for this question.