Question 1,458 of 1,546
Security and CompliancehardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to enable automatic rotation in Secrets Manager with a 30-day schedule, use the AWS-provided Lambda rotation function for RDS PostgreSQL, and ensure the application calls GetSecretValue per connection rather than caching credentials. This works because the Lambda function rotates the password in both Secrets Manager and the RDS database simultaneously, while the application’s per-connection retrieval guarantees it always fetches the current secret, avoiding stale credentials and achieving Secrets Manager rotation zero downtime for RDS. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding that zero-downtime rotation depends on the application’s retrieval pattern, not just the rotation schedule—a common trap is assuming caching credentials is safe. Remember the memory tip: “Fetch fresh, never cache” to ensure your app always uses the latest secret during rotation.

SOA-C02 Practice Question: Secrets Manager automatic rotation for RDS…

This SOA-C02 practice question tests your understanding of security and compliance. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: secrets Manager rotation. 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.

An application stores its RDS PostgreSQL credentials in AWS Secrets Manager. The security policy requires credentials to be rotated every 30 days automatically. During rotation, the application must continue to serve traffic with zero downtime. The application retrieves credentials by calling GetSecretValue at the start of each database connection. What must be configured to satisfy all requirements?

Question 1hardmultiple choice
Full question →

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

Enable automatic rotation in Secrets Manager with a 30-day schedule; use the AWS-provided Lambda rotation function for RDS PostgreSQL; ensure the application calls GetSecretValue per connection rather than caching credentials

Option A is correct because AWS Secrets Manager's automatic rotation, combined with the AWS-provided Lambda rotation function for RDS PostgreSQL, ensures credentials are rotated every 30 days without manual intervention. The application's practice of calling GetSecretValue at the start of each database connection guarantees it always retrieves the current secret, avoiding stale credentials and achieving zero downtime during rotation.

Key principle: Secrets Manager rotation

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Enable automatic rotation in Secrets Manager with a 30-day schedule; use the AWS-provided Lambda rotation function for RDS PostgreSQL; ensure the application calls GetSecretValue per connection rather than caching credentials

    Why this is correct

    The AWS-provided rotation Lambda handles the full four-step lifecycle. The 30-day rotation schedule triggers the Lambda automatically. Because the application fetches credentials fresh per connection, it starts using the new credentials immediately after AWSCURRENT switches, with no restart needed. Secrets Manager's rotation is designed for zero downtime — the new password is validated on the database before the old version is retired.

    Related concept

    Secrets Manager rotation

  • Rotate credentials manually every 30 days by updating the secret value in the console and restarting the application

    Why it's wrong here

    Manual rotation violates the 'automatic' requirement and introduces human error. Restarting the application also violates the zero-downtime requirement. The rotation schedule in Secrets Manager automates this entirely.

  • Create an EventBridge scheduled rule every 30 days that triggers a Lambda to generate a new RDS password and update both the database and the secret

    Why it's wrong here

    This approach reimplements what Secrets Manager rotation already provides natively. The custom Lambda must replicate the full four-step rotation protocol correctly, handle rollback on failure, and manage the transition window between old and new passwords. Secrets Manager's built-in rotation handles all of this.

  • Store credentials in an environment variable on the application's EC2 instance and rotate by updating the environment variable and reloading the application

    Why it's wrong here

    Environment variables are not managed by Secrets Manager, do not support automatic rotation, are not encrypted at rest by default, and appear in the EC2 console. This approach violates the Secrets Manager requirement and the zero-downtime requirement (reloading requires a restart).

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think any automated rotation (like EventBridge + Lambda) suffices, but the question specifically tests the integration of Secrets Manager's native rotation with its versioning and staging labels to achieve zero downtime.

Detailed technical explanation

How to think about this question

Secrets Manager's automatic rotation works by creating a new secret version (AWSPENDING) while keeping the current version (AWSCURRENT) active; the Lambda rotation function updates the RDS PostgreSQL password, tests the new credentials, and then marks the new version as AWSCURRENT. The application's per-connection GetSecretValue call retrieves the AWSCURRENT version, so even during rotation, it never uses a revoked credential. A subtle behavior is that if the application caches the secret, it might use the old password after rotation, causing connection failures—hence the requirement to call GetSecretValue per connection is critical.

KKey Concepts to Remember

  • Secrets Manager rotation
  • Lambda rotation function
  • RDS credentials
  • rotation schedule
  • dual-password rotation

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

Secrets Manager rotation

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Secrets Manager rotation Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Review secrets Manager rotation, then practise related SOA-C02 questions on the same topic to reinforce the concept.

Related practice questions

Related SOA-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SOA-C02 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 SOA-C02 question test?

Security and Compliance — This question tests Security and Compliance — Secrets Manager rotation.

What is the correct answer to this question?

The correct answer is: Enable automatic rotation in Secrets Manager with a 30-day schedule; use the AWS-provided Lambda rotation function for RDS PostgreSQL; ensure the application calls GetSecretValue per connection rather than caching credentials — Option A is correct because AWS Secrets Manager's automatic rotation, combined with the AWS-provided Lambda rotation function for RDS PostgreSQL, ensures credentials are rotated every 30 days without manual intervention. The application's practice of calling GetSecretValue at the start of each database connection guarantees it always retrieves the current secret, avoiding stale credentials and achieving zero downtime during rotation.

What should I do if I get this SOA-C02 question wrong?

Review secrets Manager rotation, then practise related SOA-C02 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Secrets Manager rotation

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

This SOA-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 SOA-C02 exam.