Why is an IAM role created when installing a cluster on AWS?

Question

Options

• AIn order to perform cluster related changes
• BIt is created for the installation process only, it gets deleted
• CIAM role is created for auditing purposes
• DIAM role is not created

• A
  7% (2)
• B
  3% (1)
• C
  87% (26)
• D
  3% (1)

Explanation

Heads up: The stated correct answer (C) appears to be incorrect from an AWS technical standpoint, and explaining it as correct could harm your exam preparation. Let me give you the accurate picture instead.

What actually happens: When installing a cluster on AWS (e.g., OpenShift, EKS), IAM roles are created primarily to grant cluster components the permissions needed to interact with AWS services - creating load balancers, managing EBS volumes, updating Route 53 records, etc. This aligns with option A.

Why the other options are wrong:

• B is wrong because IAM roles for cluster components persist beyond installation - they stay attached to EC2 instance profiles throughout the cluster's lifetime.
• C (stated as correct) is misleading - auditing is a secondary concern handled by CloudTrail, not the primary reason IAM roles are created during cluster installation.
• D is factually wrong; cluster installers like the OpenShift installer explicitly create IAM roles and instance profiles.

Memory tip: Think "least privilege in action" - AWS clusters need IAM roles so nodes can do things (talk to AWS APIs) without embedding static credentials. Roles = permissions to operate, not primarily to audit.

My recommendation: Double-check this question against your course material. If your exam source consistently marks C as correct, memorize it for that exam - but know that operationally, A is the accurate answer.

No community discussion yet for this question.