The answer is to use IAM roles for service accounts (IRSA) to associate an IAM role with each service’s Kubernetes service account. This is correct because IRSA enables each pod to assume a unique IAM role with fine-grained permissions, allowing the frontend service to sign AWS API requests—such as STS AssumeRole—to authenticate to the backend service without managing long-lived credentials. The backend validates the caller’s identity through IAM policies, making this the native, secure method for EKS IAM service-to-service authentication. On the DOP-C02 exam, this concept tests your understanding of workload identity integration versus older approaches like kube2iam or static AWS keys; a common trap is choosing IAM instance profiles, which grant broad node-level access instead of pod-level granularity. Remember the mnemonic: “IRSA ties a role to a service account, not a node.”
DOP-C02 Resilient Cloud Solutions Practice Question
This DOP-C02 practice question tests your understanding of resilient cloud solutions. 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.
A company runs a microservices application on Amazon EKS. The application's frontend service needs to communicate with the backend service. The DevOps team wants to implement service-to-service authentication using AWS IAM. Which method should the team use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use IAM roles for service accounts (IRSA) to associate an IAM role with each service's Kubernetes service account.
IAM roles for service accounts (IRSA) allows each Kubernetes service account to assume an IAM role with fine-grained permissions, enabling secure service-to-service authentication without managing long-lived credentials. The frontend service can use its associated IAM role to sign AWS API requests (e.g., STS AssumeRole) to authenticate to the backend service, which validates the role via IAM policies. This approach integrates natively with EKS and follows AWS best practices for workload identity.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Configure the backend service as an Amazon RDS database with IAM database authentication.
Why it's wrong here
Not applicable for service-to-service.
✗
Use AWS App Mesh with mTLS for authentication between services.
Why it's wrong here
mTLS is for encryption, not IAM integration.
✗
Create an IAM user with access keys and store them as Kubernetes secrets.
Why it's wrong here
Not best practice; long-lived credentials.
✓
Use IAM roles for service accounts (IRSA) to associate an IAM role with each service's Kubernetes service account.
Why this is correct
IRSA provides fine-grained IAM permissions to pods.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse mTLS (which provides encryption and certificate-based authentication) with IAM-based authentication, or assume that static IAM users with secrets are acceptable in Kubernetes, when IRSA is the recommended AWS-native approach for pod-level IAM integration.
Detailed technical explanation
How to think about this question
IRSA works by using an OIDC identity provider (the EKS cluster's issuer URL) to allow Kubernetes service accounts to assume IAM roles via the AWS STS AssumeRoleWithWebIdentity API. The IAM role's trust policy must reference the OIDC provider and the specific Kubernetes service account name and namespace, ensuring that only that pod can assume the role. This mechanism avoids the need to distribute AWS credentials to pods, as the kubelet and sidecar (e.g., aws-iam-token) automatically inject a projected volume with a signed JWT token that is exchanged for temporary IAM credentials.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Resilient Cloud Solutions — This question tests Resilient Cloud Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use IAM roles for service accounts (IRSA) to associate an IAM role with each service's Kubernetes service account. — IAM roles for service accounts (IRSA) allows each Kubernetes service account to assume an IAM role with fine-grained permissions, enabling secure service-to-service authentication without managing long-lived credentials. The frontend service can use its associated IAM role to sign AWS API requests (e.g., STS AssumeRole) to authenticate to the backend service, which validates the role via IAM policies. This approach integrates natively with EKS and follows AWS best practices for workload identity.
What should I do if I get this DOP-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 DOP-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 DOP-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.