The answer is to view the stack events in the CloudFormation console to identify the failed resource. This is the correct approach because every CloudFormation stack update generates a chronological list of events, and when a rollback occurs, the event for the resource that caused the failure will contain a status reason field with the specific error message and the logical resource ID. For the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding of CloudFormation’s built-in troubleshooting tools—a common trap is wasting time digging through logs or re-running the update, when the console already surfaces the root cause. A strong memory tip: think of stack events as the “black box” of your deployment—when the plane (stack) starts rolling back, the event log is the first place to check for the smoking gun.
SOA-C02 Monitoring, Logging, and Remediation Practice Question
This SOA-C02 practice question tests your understanding of monitoring, logging, and remediation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company uses AWS CloudFormation to deploy a multi-tier application. The stack includes an Application Load Balancer, Auto Scaling group, and RDS database. The SysOps administrator receives a notification that a stack update has failed. The administrator wants to investigate the failure and understand which resource caused the issue. The stack is in the UPDATE_ROLLBACK_IN_PROGRESS state. What should the administrator do to identify the failed resource?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
View the stack events in the CloudFormation console to see which resource failed and the error message.
When a CloudFormation stack update fails and enters UPDATE_ROLLBACK_IN_PROGRESS, the most direct way to identify the failed resource is to view the stack events in the CloudFormation console. Each event includes a status reason field that contains the specific error message and the logical resource ID of the resource that caused the failure, allowing the administrator to pinpoint the issue without additional investigation.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Review the stack's template in the CloudFormation console to check for syntax errors.
Why it's wrong here
Syntax errors would have been caught during validation before the update.
✗
Check the CloudWatch Logs for the EC2 instances in the Auto Scaling group.
Why it's wrong here
Instance logs are not related to CloudFormation resource creation failures.
✗
Manually re-run the update with the same parameters to see if the error recurs.
Why it's wrong here
This could cause further issues and is not diagnostic.
✓
View the stack events in the CloudFormation console to see which resource failed and the error message.
Why this is correct
Stack events provide detailed information about each resource operation.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume the failure is due to a template syntax error (Option A) or that application logs (Option B) would reveal the issue, when in fact CloudFormation events are the authoritative source for resource-level failure details during stack operations.
Detailed technical explanation
How to think about this question
CloudFormation stack events are stored in the service's event history and include a 'ResourceStatusReason' field that provides the exact error message from the underlying AWS service (e.g., an EC2 API error like 'InsufficientInstanceCapacity' or an RDS subnet group misconfiguration). The UPDATE_ROLLBACK_IN_PROGRESS state indicates that CloudFormation has already detected the failure and is automatically rolling back the changes; viewing the events reveals the first resource that entered 'UPDATE_FAILED' status, which is the root cause. This approach avoids unnecessary troubleshooting steps and aligns with AWS best practices for debugging stack operations.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Monitoring, Logging, and Remediation — This question tests Monitoring, Logging, and Remediation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: View the stack events in the CloudFormation console to see which resource failed and the error message. — When a CloudFormation stack update fails and enters UPDATE_ROLLBACK_IN_PROGRESS, the most direct way to identify the failed resource is to view the stack events in the CloudFormation console. Each event includes a status reason field that contains the specific error message and the logical resource ID of the resource that caused the failure, allowing the administrator to pinpoint the issue without additional investigation.
What should I do if I get this SOA-C02 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.