SOA-C02 Reliability and Business Continuity Practice Question
A company runs a critical production database on Amazon RDS for MySQL with a Multi-AZ deployment. The database experiences a primary instance failure. The SysOps administrator needs to understand exactly how the failover process worked and why the application experienced a longer-than-expected downtime. Which AWS service or feature should the administrator use to review detailed events and actions during the failover?
⚠ Common exam trap
Candidates often confuse AWS CloudTrail (which records API calls) with the ability to view internal service events, but CloudTrail does not capture automatic failover processes or infrastructure health events that are only available through AWS Personal Health Dashboard.
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
✓
AWS Personal Health Dashboard
AWS Personal Health Dashboard provides a personalized view of the health of AWS services and resources, including detailed event logs for RDS Multi-AZ failovers. It surfaces the exact sequence of actions (e.g., DNS record update, failover initiation, completion) and any underlying AWS infrastructure issues that caused the extended downtime, such as degraded hardware or network latency. This is the correct tool because it gives the administrator a chronological, AWS-side account of the failover process, which is not available through other services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
AWS Personal Health Dashboard
Why this is correct
The AWS Personal Health Dashboard (PHD) is the correct resource because it surfaces service health events that are specific to your AWS account and resources. For an RDS Multi-AZ failover, PHD provides a detailed event with the exact time, date, affected database instance, and the cause of the failover (e.g., infrastructure maintenance, hardware degradation, or patching). PHD also includes a timeline of activity and often links to related operational guidance, making it the authoritative source for reviewing automated failover details. Unlike generic service health dashboards, PHD filters events down to your particular resources, ensuring you see the actual failover incident that occurred.
- ✗
Amazon RDS Performance Insights
Why it's wrong here
Amazon RDS Performance Insights is a database performance tuning feature that visualizes the load on your database in terms of waits, SQL queries, and host activity. It is designed to help identify performance bottlenecks like slow queries, lock contention, or high CPU utilization, not to track infrastructure lifecycle events. While a failover could momentarily affect performance metrics, Performance Insights does not record or present the occurrence, timing, or cause of the failover itself. Therefore, it cannot be used to review failover event details.
- ✗
Amazon CloudWatch Logs
Why it's wrong here
Amazon CloudWatch Logs is a service for storing and monitoring log files, and RDS does not automatically write failover events to it. For RDS, CloudWatch Logs can contain database engine logs such as MySQL error logs, PostgreSQL logs, or SQL Server error logs, but these are application/database-level logs, not infrastructure event records. An automatic Multi-AZ failover is an infrastructure event managed by the RDS service; it is not emitted as a log entry by default. To capture RDS failover events, you would need to use RDS event notifications or Amazon EventBridge, not CloudWatch Logs directly.
- ✗
AWS CloudTrail
Why it's wrong here
AWS CloudTrail records API calls made by users, roles, or AWS services for audit and governance purposes. The automatic Multi-AZ failover process is an internal RDS service operation triggered by health checks or underlying infrastructure issues; it is not an API call that enters the CloudTrail log. CloudTrail may show supporting API calls like RebootDBInstance if a manual failover was forced, but the automatic failover itself is not represented as an API event. Thus, CloudTrail would not provide a direct record of the failover's occurrence or its root cause.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,169 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.