- A
Store the database password in AWS Secrets Manager.
Secrets Manager is designed for sensitive credentials and integrates with IAM and rotation features. It is a better fit than putting passwords in code, images, or plain variables.
- B
Have the application retrieve the secret from Secrets Manager at runtime when it needs the password.
Runtime retrieval lets the service fetch the current value without rebuilding the container. It supports password changes and reduces dependence on static configuration values.
- C
Grant the ECS task role least-privilege permission to read only that secret.
The task role gives the container temporary AWS credentials, and scoping the permission to one secret limits exposure. This is the recommended authorization model for workloads on ECS.
- D
Store the password in a plain environment variable and update it manually during maintenance windows.
Why wrong: Plain environment variables are easy to expose through logs, crash dumps, or operator mistakes. Manual updates also create avoidable downtime and operational drift.
- E
Use an IAM user access key inside the container so the database password can be embedded in code.
Why wrong: IAM users and embedded credentials are long-lived and difficult to control safely. They are not appropriate for ephemeral workloads that should use task roles instead.
Quick Answer
The answer is to grant the ECS task role least-privilege permission to read only that secret, store the database password in Secrets Manager, and have the application retrieve the secret at startup and during reconnections. This approach is correct because AWS Secrets Manager encrypts the password at rest using AWS KMS and supports automatic rotation, ensuring the credential is never exposed in plaintext or hardcoded in the container image. On the SAA-C03 exam, this scenario tests your understanding of how to decouple sensitive configuration from compute using IAM roles and a dedicated secrets service—a common trap is assuming environment variables or a parameter store without rotation are sufficient. Remember the key chain: the task role grants access, Secrets Manager holds the secret, and the application code calls the API. A useful memory tip is "Role, Store, Retrieve"—the three actions map directly to IAM, Secrets Manager, and the application’s runtime call.
SAA-C03 Design Secure Architectures Practice Question
This SAA-C03 practice question tests your understanding of design secure architectures. 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 containerized service on Amazon ECS connects to a database with a password that must never be stored in plaintext or hardcoded in the image. The application reads the password at startup and occasionally reconnects later, so it needs to retrieve the current secret when needed. Which three actions should the architect take? Select three.
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"never"Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Store the database password in AWS Secrets Manager.
AWS Secrets Manager is the correct service for storing sensitive data like database passwords because it provides encryption at rest (using AWS KMS) and automatic rotation capabilities. By storing the password in Secrets Manager, the architect ensures it is never exposed in plaintext or hardcoded in the container image, meeting the security requirement.
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.
- ✓
Store the database password in AWS Secrets Manager.
Why this is correct
Secrets Manager is designed for sensitive credentials and integrates with IAM and rotation features. It is a better fit than putting passwords in code, images, or plain variables.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Have the application retrieve the secret from Secrets Manager at runtime when it needs the password.
Why this is correct
Runtime retrieval lets the service fetch the current value without rebuilding the container. It supports password changes and reduces dependence on static configuration values.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Grant the ECS task role least-privilege permission to read only that secret.
Why this is correct
The task role gives the container temporary AWS credentials, and scoping the permission to one secret limits exposure. This is the recommended authorization model for workloads on ECS.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store the password in a plain environment variable and update it manually during maintenance windows.
Why it's wrong here
Plain environment variables are easy to expose through logs, crash dumps, or operator mistakes. Manual updates also create avoidable downtime and operational drift.
- ✗
Use an IAM user access key inside the container so the database password can be embedded in code.
Why it's wrong here
IAM users and embedded credentials are long-lived and difficult to control safely. They are not appropriate for ephemeral workloads that should use task roles instead.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates might think environment variables or IAM access keys are acceptable for secrets, but the exam requires using a dedicated secrets management service like Secrets Manager to avoid plaintext exposure and enable rotation.
Detailed technical explanation
How to think about this question
AWS Secrets Manager integrates with AWS KMS to encrypt secrets at rest and supports automatic rotation via AWS Lambda, which can be scheduled to rotate the database password without application downtime. The ECS task role uses an IAM role attached to the task definition, allowing the application to call the GetSecretValue API with least-privilege permissions, and the secret is cached locally by the AWS SDK to reduce latency on subsequent retrievals.
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.
- →
Design Secure Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Secure Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Store the database password in AWS Secrets Manager. — AWS Secrets Manager is the correct service for storing sensitive data like database passwords because it provides encryption at rest (using AWS KMS) and automatic rotation capabilities. By storing the password in Secrets Manager, the architect ensures it is never exposed in plaintext or hardcoded in the container image, meeting the security requirement.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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 →
Same concept, more angles
1 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A containerized service on Amazon ECS connects to a database with a password that must never be stored in plaintext or hardcoded in the image. The application reads the password at startup and occasionally reconnects later, so it needs to retrieve the current secret when needed. Which three actions should the architect take? Select three.
medium- ✓ A.Store the database password in AWS Secrets Manager.
- ✓ B.Have the application retrieve the secret from Secrets Manager at runtime when it needs the password.
- ✓ C.Grant the ECS task role least-privilege permission to read only that secret.
- D.Store the password in a plain environment variable and update it manually during maintenance windows.
- E.Use an IAM user access key inside the container so the database password can be embedded in code.
Why A: AWS Secrets Manager is the correct service for securely storing and automatically rotating database credentials. It eliminates the need to hardcode secrets in the container image or store them in plaintext. The application retrieves the secret at runtime via the AWS SDK, ensuring the current password is always used.
Last reviewed: Jun 11, 2026
This SAA-C03 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 SAA-C03 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.