SOA-C02 Monitoring, Logging, and Remediation Practice Question
A SysOps administrator is troubleshooting an issue where an EC2 instance has failed a status check. The instance is still running but is unresponsive. Which THREE actions should the administrator take to diagnose and resolve the issue? (Choose THREE.)
⚠ Common exam trap
Many candidates confuse 'reboot' with 'stop/start' — rebooting does not change the underlying host, while stopping and starting does, which is the key recovery action for host-level failures.
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
✓
Check the system status checks in the EC2 console.
System status checks (Option B) monitor the underlying physical host for issues like network or power loss, while instance status checks (like system log in Option C) detect OS-level problems. Reviewing the system log helps identify kernel panics or boot failures. Stopping and starting the instance (Option E) forces a migration to a new physical host, which can resolve host-level impairments without losing the instance's configuration or data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reboot the instance.
Why it's wrong here
Rebooting the instance performs a soft reset of the guest operating system but does not migrate the workload to a different physical host. If the underlying host has degraded hardware or lost network connectivity, the system status check will continue to fail after a reboot because the instance remains on the same problematic host. Reboot is appropriate for addressing OS-level hangs or software hangs, not for resolving AWS-detected infrastructure faults.
- ✓
Check the system status checks in the EC2 console.
Why this is correct
Checking the system status checks in the EC2 console is the correct first triage step because these checks directly report on the health of the underlying physical host, network connectivity, and power delivery. A failed system status check (e.g., 'System reachability' or 'Instance connectivity') indicates a hardware-level issue that is independent of the guest OS, guiding you toward a stop/start recovery rather than a reboot. CloudWatch metrics for status checks should also be reviewed to confirm the duration and pattern of the failure.
- ✓
Review the instance system log (console output).
Why this is correct
Reviewing the instance system log (console output) provides visibility into the guest operating system's boot sequence, kernel messages, and initialization logs. This is primarily useful for diagnosing software-level or OS-level failures such as kernel panics, filesystem corruption, or failing disk mounts. However, if the problem is with the underlying host hardware, the guest OS log often shows no error because the VM never receives proper network connectivity or CPU resources; thus, it is a complementary diagnostic but not the definitive health check for host issues.
- ✗
Restore the instance from the latest AMI.
Why it's wrong here
Restoring from the latest AMI is a disaster-recovery action that replaces the entire instance with a fresh one built from a saved image, which is excessive and destructive for a running-instance hardware failure. It would lose all data on instance store volumes and any changes made after the snapshot, and it does not directly address the underlying host fault that is already in progress. This action should be reserved for scenarios like corruption or accidental deletion, not for troubleshooting a single degraded host.
- ✓
Stop and start the instance (recovery action).
Why this is correct
Stopping and starting the instance is the AWS recovery action that provisions the instance on a new physical host, resolving issues caused by failed hardware, network components, or degraded power on the original host. This process preserves the instance ID, EBS volumes, IP addresses, and all data on EBS-backed storage, but it does not preserve instance store volumes. After performing stop/start, you should verify that the system status checks transition to '2/2 passed' to confirm the underlying host issue has been resolved.
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.