Sample question 1 · Design Cost-Optimized Architectures (20%)
Patchline Systems is a SaaS startup headquartered in Germany that provides automated patch-cycle orchestration to regulated financial services clients across the EU. The company stores patch compliance records, vulnerability scores, and audit trails in Amazon Aurora MySQL. The database is provisioned as a two-node Aurora cluster (writer + reader) running continuously. The CFO has raised a concern in the quarterly governance review: the Aurora cluster accounts for 38% of total AWS spend, yet telemetry shows the database receives zero queries between 22:00 and 06:00 CET every night and is lightly loaded on weekends. The Head of Engineering argues that the cluster must remain available for on-call engineers who may need ad-hoc queries at any hour. The solutions architect must present a cost-optimized design to the steering committee that balances availability for on-call access with elimination of unnecessary idle spend, without changing the MySQL wire protocol used by the application. As the solutions architect presenting to the Patchline Systems steering committee, which design best balances cost optimization during idle hours with on-call availability and MySQL protocol compatibility?
- A. Convert the Aurora MySQL cluster to Aurora Serverless v2 with a minimum ACU of 0.5 and enable the cluster to scale to zero during defined idle windows, while retaining the MySQL-compatible cluster endpoint for on-call engineers and the application.
- B. Delete the Aurora reader node to eliminate its cost and rely solely on the writer node, scheduling a Lambda function to create a new reader node each morning using the AWS SDK.
- C. Migrate the Aurora MySQL cluster to Amazon RDS for MySQL with Multi-AZ enabled and purchase a 3-year Reserved Instance to reduce the hourly rate.
- D. Enable Aurora Auto Scaling on the reader node to scale reader replicas to zero during idle hours, while keeping the writer node provisioned at full capacity around the clock.
View answer & explanation
Correct answer: A. Convert the Aurora MySQL cluster to Aurora Serverless v2 with a minimum ACU of 0.5 and enable the cluster to scale to zero during defined idle windows, while retaining the MySQL-compatible cluster endpoint for on-call engineers and the application.
[Domain 4 - Design Cost-Optimized Architectures, Subtopic 4 - Design Cost-Optimized Architectures - Area 1 - Serverless DB] Core Concept: Design cost-optimized database solutions. requires applying serverless db in the context of the scenario, consistent with the official (ISC)² exam outline. Correct Answer (A): Convert the Aurora MySQL cluster to Aurora Serverless v2 with a minimum ACU of 0.5 and enable the cluster to scale to zero during defined idle windows, while retaining the MySQL-compatible cluster endpoint for on-call engineers and the application. Why the other options are incorrect: Option B: Dynamically deleting and recreating a reader node via Lambda introduces operational complexity, potential data consistency risks, and cold-start delays that are unacceptable for on-call engineers who need immediate ad-hoc query access; it also does not address the writer node's idle cost. Option C: Migrating to RDS for MySQL with Multi-AZ and a Reserved Instance locks Patchline into a fixed provisioned cost for three years and does not reduce idle spend — it simply lowers the per-hour rate, which is a pricing optimization rather than an architectural one that addresses the 38% spend concern. Option D: Aurora Auto Scaling manages the number of reader replicas based on load metrics but cannot scale the writer node; the writer node — which is the primary cost driver in a two-node cluster — remains fully provisioned and billed at full capacity throughout the idle window.