A county wants a managed relational database that is compatible with MySQL or PostgreSQL and is positioned as Amazon's cloud-native relational engine. Which service should they recognize?
Select an answer to reveal the explanation.
Short Explanation
Aurora is AWS's cloud-built relational engine that still speaks MySQL or PostgreSQL—so apps that already know those dialects can feel at home. MQ is messaging, CloudWatch Logs is log storage, and WAF is a web firewall—none of those are your SQL database.
Full Explanation
A county that wants a managed relational database compatible with MySQL or PostgreSQL and positioned as Amazon’s cloud-native relational engine should recognize Amazon Aurora. Aurora is AWS’s managed relational database engine designed for cloud environments, with MySQL and PostgreSQL compatibility, and it is commonly contrasted with community engines running on RDS as well as with self-managed databases on EC2.
Amazon MQ is a managed message broker, not a MySQL-compatible relational database. Amazon CloudWatch Logs stores and queries logs; it is not a PostgreSQL-compatible engine. AWS WAF filters web requests and is not a managed relational store for SQL applications.
Exam caveat: Aurora = cloud-native managed relational with MySQL/PostgreSQL compatibility. RDS also manages several engines; when the stem stresses Amazon’s cloud-native relational engine, Aurora is the intended recognition item.
Operational check: select Aurora MySQL or Aurora PostgreSQL compatibility based on the county application, test feature compatibility early, configure Multi-AZ / Aurora replicas as needed, and document backup retention against records-retention schedules before migrating production finance or permitting databases.