The correct answer is to enable audit logging for the cluster, restrict kubectl access via IAM, and use a private endpoint for the API server. These three actions directly address EKS cluster security best practices by ensuring that all API calls are monitored for suspicious activity, only authorized IAM roles can manage the cluster through kubectl, and the Kubernetes API server is not exposed to the public internet, reducing the attack surface. On the AWS Certified Security Specialty SCS-C02 exam, this question tests your understanding of the shared responsibility model for EKS and common misconfigurations; a frequent trap is assuming the default VPC is inherently insecure or that cluster-admin roles are acceptable for daily operations. Remember the mnemonic “PAL” for Private endpoint, Audit logging, and Least privilege (via IAM) to recall the three pillars of securing an EKS control plane.
SCS-C02 Infrastructure Security Practice Question
This SCS-C02 practice question tests your understanding of infrastructure security. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Which THREE actions will improve the security of an Amazon EKS cluster?
A security engineer is reviewing the security of an Amazon EKS cluster. The cluster is used to run containerized applications. Which three actions should the engineer take to improve the security of the cluster?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Restrict access to the cluster using AWS IAM authentication for kubectl.
Options A, C, and E are correct. Enabling audit logging helps monitor API calls. Restricting kubectl access via IAM ensures only authorized users can manage the cluster. Using a private endpoint for the API server prevents exposure to the internet. Option B is incorrect because using the default VPC is not inherently insecure; custom VPCs can be used. Option D is incorrect because cluster-admin is too permissive; least privilege should be applied.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Restrict access to the cluster using AWS IAM authentication for kubectl.
Why this is correct
IAM provides fine-grained access control to the cluster.
Related concept
Authentication checks who the user is.
✗
Use the default VPC for the cluster.
Why it's wrong here
Using the default VPC may not follow security best practices; custom VPCs are recommended.
✓
Configure the cluster API server endpoint to be private.
Why this is correct
A private endpoint prevents internet access to the API server.
Related concept
Authentication checks who the user is.
✗
Grant the cluster-admin role to all developers.
Why it's wrong here
This violates least privilege principle.
✓
Enable audit logging for the cluster.
Why this is correct
Audit logs help detect and investigate suspicious activities.
Related concept
Authentication checks who the user is.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Got this wrong? Here's your next step.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SCS-C02 questions on access control and AAA configuration.
Infrastructure Security — This question tests Infrastructure Security — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Restrict access to the cluster using AWS IAM authentication for kubectl. — Options A, C, and E are correct. Enabling audit logging helps monitor API calls. Restricting kubectl access via IAM ensures only authorized users can manage the cluster. Using a private endpoint for the API server prevents exposure to the internet. Option B is incorrect because using the default VPC is not inherently insecure; custom VPCs can be used. Option D is incorrect because cluster-admin is too permissive; least privilege should be applied.
What should I do if I get this SCS-C02 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SCS-C02 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This SCS-C02 practice question is part of Courseiva's free Amazon Web Services 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 SCS-C02 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.