DOP-C02 Practice Question 100: OpsCenter OpsItems Aggregation
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 10 · question 10 of 10
An operations team receives operational problems from several sources: CloudWatch alarms firing on production services, AWS Config rules reporting noncompliant resources, and manual reports from engineers who spot something wrong. Today these land in different tools, so nothing gives the team a single place to see, prioritize, investigate, and track resolution of every open issue, along with the related resource, alarm, and change history for each one.
Which AWS Systems Manager capability should they adopt?
Show answer and explanation
Answer:
OpsCenter is built to be the single pane of glass for operational work items. CloudWatch alarms, AWS Config rule noncompliance, and manually created issues can all generate or be associated with an OpsItem, and OpsCenter attaches related resources, related OpsItems, and contextual data such as recent changes to each one, so an engineer can investigate and resolve an issue from a single record without visiting several separate consoles.
Option A automates remediation for individual alarms, but running a runbook does not create any aggregated, trackable record of the issue, and it does nothing for issues that originate from Config or from a manual report.
Option B repurposes Parameter Store, a configuration data store, as an ad hoc issue tracker using tags; it has no workflow, status, or automatic ingestion from CloudWatch or Config, so it does not meet the aggregation and tracking requirement.
Option D reports what software and configuration exist on managed instances at a point in time, which is useful for inventory and compliance auditing, but it does not track operational issues, alarms, or their resolution status at all.
Reference: AWS Systems Manager OpsCenter