Cost-Optimized Managed PostgreSQL for Developers

SAA-C03 By islever Editorial Last updated

Short answer

C Create an Amazon Aurora Serverless cluster and use AWS Service Catalog to allow developers to launch databases with default capacity settings.

Question

A large company wants to provide its globally located developers separate, limited size, managed PostgreSQL databases for development purposes. The databases will be low volume. The developers need the databases only when they are actively working. Which solution will meet these requirements MOST cost-effectively?
  1. Give the developers the ability to launch separate Amazon Aurora instances. Set up a process to shut down Aurora instances at the end of the workday and to start Aurora instances at the beginning of the next workday.
  2. Develop an AWS Service Catalog product that enforces size restrictions for launching Amazon Aurora instances. Give the developers access to launch the product when they need a development database.
  3. Create an Amazon Aurora Serverless cluster. Develop an AWS Service Catalog product to launch databases in the cluster with the default capacity settings. Grant the developers access to the product. Correct Answer
  4. Monitor AWS Trusted Advisor checks for idle Amazon RDS databases. Create a process to terminate identified idle RDS databases.

Key Takeaways

The question tests the understanding of pay-per-use database scaling versus provisioned instances, with the common trap being the assumption that separate physical databases are required for isolation.

This question tests the selection of a cost-effective managed database solution for intermittent developer usage, establishing that Amazon Aurora Serverless combined with AWS Service Catalog is the optimal choice.

Common mistake: Many candidates choose Option B because they interpret 'separate' databases as requiring distinct EC2-backed instances, missing the cost inefficiency of always-on provisioned Aurora compared to Serverless.

Expert Analysis

Why the Answer Is Correct

Option C is correct because it addresses both the technical requirement for managed PostgreSQL and the financial constraint of intermittent use. Amazon Aurora Serverless automatically starts up, shuts down, and scales capacity based on application needs, allowing you to pay only for the compute resources consumed when the database is active. This eliminates costs during idle periods, which aligns perfectly with developers working only when actively needed. AWS Service Catalog is used to provide a controlled self-service portal, ensuring developers can launch these databases within defined size limits without needing deep administrative privileges.

Why the Other Options Are Wrong

Options A and B involve provisioning fixed-capacity Amazon Aurora DB instances. These instances run continuously (unless manually stopped) and incur hourly charges regardless of utilization, making them significantly more expensive for low-volume, sporadic workloads. Option D suggests terminating idle RDS databases via Trusted Advisor; however, this destroys the data and environment, requiring recreation from backups or snapshots, which does not meet the need for immediate access when developers are working. Furthermore, manual termination processes are error-prone and do not provide the seamless self-service experience offered by Service Catalog.

Community Comment Notes

Community consensus strongly favors Option C. As user NSA_Poker noted, "Aurora instances & Amazon RDS use On-Demand or Reserved INSTANCES... These are more expensive than a serverless solution." Several users highlighted that Aurora Serverless "automatically starts up, shuts down & scales," which is ideal for development environments. Some confusion existed regarding Option B, with users like Johnoppong101 arguing that "Each developer needs a separate DB" implies isolated instances, but in the context of AWS architecture exams, logical separation within a Serverless cluster is sufficient and far more cost-effective than maintaining multiple provisioned clusters.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

Always look for keywords like 'cost-effectively', 'intermittent', or 'sporadic' when evaluating storage and database options. If the workload is not constant, consider Serverless or Spot instances over Provisioned/On-Demand to avoid paying for idle capacity.

Frequently Asked Questions

Why isn't Option B better for providing separate databases?

Option B uses provisioned Aurora instances which run 24/7 and incur full hourly costs even when idle. For intermittent use, this is far less cost-effective than Aurora Serverless, which scales to zero.

Does Aurora Serverless support logical separation for multiple developers?

Yes. You can create multiple logical databases within a single Aurora Serverless cluster. Each developer gets their own schema/database namespace, satisfying the 'separate' requirement without needing separate physical instances.

More SAA-C03 FAQ →

Community Votes

C
79%
B
21%

79% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 13 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 13

  1. NSA_Poker 👍 7 Answered C
    (A,B,D) eliminated. Aurora instances & Amazon RDS use On-Demand or Reserved INSTANCES. These are more expensive than a serverless solution. (C) is correct. Amazon Aurora Serverless automatically starts up, shuts down & scales capacity up or down based on your application's needs; you pay only for capacity consumed.
  2. kelmryan1 👍 6
    Yes but its asking for the most cost effective. B would cause frustration for developers if it was terminated unexpectedly. The answer should be C so developers can easily access when they are needed and auto scales based on demand
  3. LeonSauveterre 👍 3 Answered C
    A - Aurora = Overkill and expensive. B - Just like A. C - Aurora Serverless scales based on usage and can automatically scale down to zero when the database is not in use. This is ideal for a development environment where databases are only needed during active work hours. D - Money is not an issue here I think. The real problem is - there’s no guarantee that the database would be automatically available when the developers need it. The need for a manual process to monitor and terminate idle databases introduces operational overhead and the potential for human error.
  4. [Removed] 👍 3 Answered C
    Aurora Serverless = inicia, encerra e escala a capacidade automaticamente de acordo com as necessidades. AWS Service Catalog = catalogo de serviços que usuarios podem utilizar, dentro das configurações permitidas. https://aws.amazon.com/pt/rds/aurora/serverless/ https://aws.amazon.com/pt/servicecatalog/
  5. mk168898 👍 3 Answered C
    when i see "managed PostgreSQL databases", i immediately look for serverless
Show 8 more comments
  1. Scheldon 👍 2
    AnswerC Using Aurora Serverless solution + AWS Service Catalog features seems to be a good idea https://aws.amazon.com/rds/aurora/serverless/ https://aws.amazon.com/servicecatalog/features/
  2. Hkayne 👍 2 Answered B
    With AWS Service Catalog, you can meet your compliance requirements while making sure your customers can quickly deploy the cloud resources they need.
  3. ike001 👍 2
    Answer C: We know we require Service Catalog. This option provides workflow no how it works
  4. Johnoppong101 👍 1
    Guys, listen to the question, each developer -> a separate managed PostgreSQL DB. this is the task. Then Most cost-effective comes. If you get a cheaper thing that does not fulfull the task, you are wrong. Question: Can each developer get a separate DB for himself from the cluster?
  5. b3b5fdd 👍 1 Answered B
    I think the answer correct is B as the database should be managed by the developer and Each developer needs a separate DB.
  6. Johnoppong101 👍 1 Answered B
    Requirement: Each developer needs a separate DB. In a cluster, DB is shared among developers.
  7. f07ed8f 👍 1 Answered B
    Only option B can have limited size database
  8. Sergiuss95 👍 3 Answered C
    I thin is c

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide