nerdexam
Amazon

SAA-C03 · Question #148

A company is planning to migrate an on-premises online transaction processing (OLTP) database that uses MySQL to an AWS managed database management system. Several reporting and analytics…

The correct answer is A. Aurora MySQL: Handles OLTP workloads efficiently with built-in replication and auto-scaling. The company needs to migrate an OLTP MySQL database to a managed AWS service that can efficiently handle read-heavy surges periodically.

Submitted by krish.m· Mar 4, 2026Design High-Performing Architectures

Question

A company is planning to migrate an on-premises online transaction processing (OLTP) database that uses MySQL to an AWS managed database management system. Several reporting and analytics applications use the on-premises database heavily on weekends and at the end of each month. The cloud-based solution must be able to handle read-heavy surges during weekends and at the end of each month. Which solution will meet these requirements?

Options

  • AAurora MySQL: Handles OLTP workloads efficiently with built-in replication and auto-scaling
  • BEC2 with MySQL: Requires heavy manual maintenance and does not scale seamlessly.
  • CRDS for MySQL: Limited in auto-scaling compared to Aurora.
  • DRedshift: Primarily for OLAP, not suitable for OLTP workloads.

How the community answered

(25 responses)
  • A
    72% (18)
  • B
    4% (1)
  • C
    16% (4)
  • D
    8% (2)

Why each option

The company needs to migrate an OLTP MySQL database to a managed AWS service that can efficiently handle read-heavy surges periodically.

AAurora MySQL: Handles OLTP workloads efficiently with built-in replication and auto-scalingCorrect

Amazon Aurora MySQL is a fully managed, MySQL-compatible relational database service designed for high performance and availability, ideal for OLTP workloads. Its architecture includes built-in replication and auto-scaling of read replicas, allowing it to efficiently handle read-heavy surges without manual intervention, addressing the requirement for handling weekend and month-end spikes.

BEC2 with MySQL: Requires heavy manual maintenance and does not scale seamlessly.

Running MySQL on EC2 instances requires significant manual management for patching, backups, and scaling, making it less efficient and more operationally intensive than a managed service.

CRDS for MySQL: Limited in auto-scaling compared to Aurora.
DRedshift: Primarily for OLAP, not suitable for OLTP workloads.

Concept tested: AWS managed relational database services, read scaling

Source: https://aws.amazon.com/rds/aurora/

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SAA-C03 Practice