What access control mechanisms are crucial for implementing data permissions in an ECS cluster for client access?

Question

Options

• ARole-Based Access Control (RBAC)
• BNetwork-based ACLs
• CPhysical security of the data center
• DIdentity and Access Management (IAM) policies

• A
  91% (49)
• B
  6% (3)
• C
  4% (2)

Explanation

RBAC (A) and IAM policies (D) are the correct choices because they directly govern who can access what data within an ECS cluster - RBAC assigns permissions based on user roles within the cluster (e.g., Kubernetes RBAC for ECS task definitions and resources), while IAM policies control AWS-level permissions for services, users, and roles interacting with the ECS cluster and its underlying data. Together, they form a layered identity-based access control model that enforces least privilege at both the application and infrastructure levels.

B (Network-based ACLs) is wrong because ACLs control network traffic flow (which IPs/ports can communicate), not data-level permissions - they can't distinguish between authenticated users or enforce role-specific data access. C (Physical security) is a red herring; it protects hardware in the data center and is entirely irrelevant to logical data permissions within a cluster.

Memory tip: Think "ID check at the door" - IAM checks your AWS identity before you enter the building, RBAC checks your role-based badge once you're inside. Network ACLs are the fence outside, not the bouncer checking credentials.

No community discussion yet for this question.