An operations team needs a saved view of ALB, EC2, and RDS metrics and existing alarms across Regions in one AWS account.
Their IAM users and roles have the required read access. Compare the same incident interval without switching between service consoles.
Which feature is most appropriate?
Place regional metric and alarm widgets in a CloudWatch dashboard for a common team view.
Detailed explanation
It combines alarm states but does not replace a screen of metric time series.
It combines alarm states but does not replace a screen of metric time series.
An endpoint check does not provide the required EC2 and RDS metric view.
An endpoint check does not provide the required EC2 and RDS metric view.
A saved view combines resource signals for comparison over a common interval.
A saved view combines resource signals for comparison over a common interval.
This does not create the required saved shared screen.
This does not create the required saved shared screen.
Check official documentation
Compare the following points with the official documentation.
Review dashboard widgets, regional metric selection, and read permissions.
Official references
What to confirm
Align metric scope and time while separating visualization from alarm notification.
Key points
- CloudWatch dashboard
- Widget
- Cross-service metrics
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-04.
Foundation review
Align resources and time
Specify metric namespace, resource dimensions, and Region. Match time windows, periods, and statistics; CPU percentages and event counts have different units.
A view does not configure detection
Dashboards combine metrics and alarms across Regions. Saving a view does not create new alarm evaluation or notification. IAM access governs the team's viewing.