- A
Store the password in Systems Manager Parameter Store as a SecureString and grant the ECS task role GetParameter only for that parameter ARN. Have the application call GetParameter on each request or on a short refresh interval.
Why wrong: Parameter Store can support secure storage, but the question explicitly emphasizes Secrets Manager controls and rotation; also, redeploy avoidance depends on application refresh behavior and secret rotation integration.
- B
Store the password in AWS Secrets Manager. Configure rotation for the secret. Grant the ECS task role secretsmanager:GetSecretValue for only that secret ARN. Update the application to fetch the secret at runtime and cache it briefly.
Secrets Manager provides encrypted-at-rest storage and supports managed rotation. ECS task roles provide least-privilege access without static keys. Fetching at runtime with brief caching supports rotation without redeploying the task definition.
- C
Store the password in a local file within the container image and mount it as a Docker secret at build time to avoid environment variables.
Why wrong: Including credentials in images increases leakage risk and does not provide a robust rotation mechanism. Least-privilege access via IAM roles is not used effectively.
- D
Store the password in an S3 bucket with server-side encryption and allow all ECS tasks to read it using a broad IAM policy on the bucket prefix.
Why wrong: S3 is not a purpose-built secrets storage service, and broad IAM permissions violate least privilege. Rotation and secret lifecycle controls are weaker compared with Secrets Manager.
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 web service on Amazon ECS reads a database password at startup. Today, the password is stored in a plain environment variable and updated manually. Auditors require that credentials: (1) are encrypted at rest using AWS-managed controls, (2) can be rotated without redeploying the task definition, and (3) are accessible only to the running task via least-privilege permissions.
Which solution best meets these requirements?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"least"Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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 password in AWS Secrets Manager. Configure rotation for the secret. Grant the ECS task role secretsmanager:GetSecretValue for only that secret ARN. Update the application to fetch the secret at runtime and cache it briefly.
Option B is correct because AWS Secrets Manager encrypts secrets at rest using AWS KMS (AWS-managed key by default), supports automatic rotation without requiring a task definition redeploy, and allows least-privilege access by granting the ECS task role only secretsmanager:GetSecretValue for the specific secret ARN. The application fetches the secret at runtime and caches it briefly, satisfying all three auditor requirements.
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 password in Systems Manager Parameter Store as a SecureString and grant the ECS task role GetParameter only for that parameter ARN. Have the application call GetParameter on each request or on a short refresh interval.
Why it's wrong here
Parameter Store can support secure storage, but the question explicitly emphasizes Secrets Manager controls and rotation; also, redeploy avoidance depends on application refresh behavior and secret rotation integration.
When this WOULD be correct
If the requirements did not include automatic rotation and allowed the application to fetch the secret on each request (e.g., for a non-critical config value that changes infrequently), Parameter Store SecureString with IAM least-privilege would be a valid, cost-effective solution.
- ✓
Store the password in AWS Secrets Manager. Configure rotation for the secret. Grant the ECS task role secretsmanager:GetSecretValue for only that secret ARN. Update the application to fetch the secret at runtime and cache it briefly.
Why this is correct
Secrets Manager provides encrypted-at-rest storage and supports managed rotation. ECS task roles provide least-privilege access without static keys. Fetching at runtime with brief caching supports rotation without redeploying the task definition.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Store the password in a local file within the container image and mount it as a Docker secret at build time to avoid environment variables.
Why it's wrong here
Including credentials in images increases leakage risk and does not provide a robust rotation mechanism. Least-privilege access via IAM roles is not used effectively.
When this WOULD be correct
This option would be correct if the requirement was to avoid any runtime dependency on AWS services for secret retrieval (e.g., offline or air-gapped environment) and rotation was not required, with the password being static and updated only via image rebuild.
- ✗
Store the password in an S3 bucket with server-side encryption and allow all ECS tasks to read it using a broad IAM policy on the bucket prefix.
Why it's wrong here
S3 is not a purpose-built secrets storage service, and broad IAM permissions violate least privilege. Rotation and secret lifecycle controls are weaker compared with Secrets Manager.
When this WOULD be correct
This option would be correct if the requirement was to store a large, static configuration file (e.g., a machine learning model) that is encrypted at rest, accessed by multiple tasks, and does not require rotation or strict least-privilege per task.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Store the password in AWS Secrets Manager. Configure rotation for the secret. Grant the ECS task role secretsmanager:GetSecretValue for only that secret ARN. Update the application to fetch the secret at runtime and cache it briefly.Correct answer▾
Why this is correct
Secrets Manager provides encrypted-at-rest storage and supports managed rotation. ECS task roles provide least-privilege access without static keys. Fetching at runtime with brief caching supports rotation without redeploying the task definition.
✗Store the password in Systems Manager Parameter Store as a SecureString and grant the ECS task role GetParameter only for that parameter ARN. Have the application call GetParameter on each request or on a short refresh interval.Wrong answer — click to see why▾
Why this is wrong here
Option A requires the application to call GetParameter on each request or a short refresh interval, which does not meet the requirement for credentials to be rotated without redeploying the task definition. Additionally, Parameter Store SecureString does not support automatic rotation, failing the rotation requirement.
★ When this WOULD be the correct answer
If the requirements did not include automatic rotation and allowed the application to fetch the secret on each request (e.g., for a non-critical config value that changes infrequently), Parameter Store SecureString with IAM least-privilege would be a valid, cost-effective solution.
Why candidates choose this
Candidates may confuse Parameter Store SecureString with Secrets Manager, thinking both support encryption and IAM policies, and overlook the specific rotation requirement. They might also assume that caching the secret is unnecessary or that Parameter Store is sufficient for secrets management.
✗Store the password in a local file within the container image and mount it as a Docker secret at build time to avoid environment variables.Wrong answer — click to see why▾
Why this is wrong here
Storing the password in a local file within the container image at build time prevents rotation without redeploying the task definition, violating requirement (2). It also does not use AWS-managed encryption controls for the password at rest, as the image may be stored in Amazon ECR without encryption.
★ When this WOULD be the correct answer
This option would be correct if the requirement was to avoid any runtime dependency on AWS services for secret retrieval (e.g., offline or air-gapped environment) and rotation was not required, with the password being static and updated only via image rebuild.
Why candidates choose this
Candidates may think that embedding secrets in the image as a file is more secure than environment variables and avoids network calls, but they overlook the rotation and redeployment constraints.
✗Store the password in an S3 bucket with server-side encryption and allow all ECS tasks to read it using a broad IAM policy on the bucket prefix.Wrong answer — click to see why▾
Why this is wrong here
Option D fails because it does not support credential rotation without redeploying the task definition, and the broad IAM policy on the bucket prefix violates least-privilege permissions by allowing all ECS tasks to read the password.
★ When this WOULD be the correct answer
This option would be correct if the requirement was to store a large, static configuration file (e.g., a machine learning model) that is encrypted at rest, accessed by multiple tasks, and does not require rotation or strict least-privilege per task.
Why candidates choose this
Candidates may think S3 with SSE provides encryption at rest and is easy to set up, overlooking the lack of rotation support and the overly permissive access policy that violates least-privilege.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may choose Option A (Parameter Store) because it also supports SecureString and IAM policies, but they overlook that Secrets Manager is the only service that natively provides automatic rotation without additional custom infrastructure, which is explicitly required by the auditors.
Detailed technical explanation
How to think about this question
AWS Secrets Manager integrates with AWS KMS for envelope encryption; the secret is encrypted with a KMS key (either AWS-managed or customer-managed) and decrypted only when the GetSecretValue API is called with the correct IAM permissions. The ECS task role is an IAM role assumed by the ECS agent on behalf of the container, and the application can cache the secret in memory for a short TTL (e.g., 5 minutes) to reduce API calls while still allowing rotation to take effect on the next fetch. Under the hood, Secrets Manager uses a CloudFormation-backed custom resource or a Lambda function to perform rotation, updating the secret version without changing the ARN.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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 password in AWS Secrets Manager. Configure rotation for the secret. Grant the ECS task role secretsmanager:GetSecretValue for only that secret ARN. Update the application to fetch the secret at runtime and cache it briefly. — Option B is correct because AWS Secrets Manager encrypts secrets at rest using AWS KMS (AWS-managed key by default), supports automatic rotation without requiring a task definition redeploy, and allows least-privilege access by granting the ECS task role only secretsmanager:GetSecretValue for the specific secret ARN. The application fetches the secret at runtime and caches it briefly, satisfying all three auditor requirements.
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: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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 →
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
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.