70-246 · Question #148
Your network contains an Active Directory domain named contoso.com. The domain contains a domain controller named DC1 and member servers named Server1 and Server2. Server1 has System Center 2012 R2…
The correct answer is B. Configure a filter of MonitorObjectName equals Monitor1. D. Add the Monitor Alert activity and configure triggers for the alert. To trigger a runbook when Alert1 fires, you must add the Monitor Alert activity and filter by the monitor name (MonitorObjectName equals Monitor1) in System Center Orchestrator.
Question
Your network contains an Active Directory domain named contoso.com. The domain contains a domain controller named DC1 and member servers named Server1 and Server2. Server1 has System Center 2012 R2 Operations Manager installed. Server2 has System Center 2012 R2 Orchestrator installed. Orchestrator has the System Center Integration Pack for System Center 2012 R2 Operations Manager installed. In Operations Manager, you have a monitor named Monitor1 that triggers an alert named Alert1. You need to ensure that when Alert1 is triggered, a custom runbook starts. Which two actions should you perform from Orchestrator? Each correct answer presents part of the solution.
Options
- AConfigure a filter of PrincipalName equals Alert1.
- BConfigure a filter of MonitorObjectName equals Monitor1.
- CAdd the Get Alert activity.
- DAdd the Monitor Alert activity and configure triggers for the alert.
- EConfigure a filter of Name equals Alert1.
How the community answered
(26 responses)- A12% (3)
- B54% (14)
- C27% (7)
- E8% (2)
Why each option
To trigger a runbook when Alert1 fires, you must add the Monitor Alert activity and filter by the monitor name (MonitorObjectName equals Monitor1) in System Center Orchestrator.
PrincipalName refers to the name of the target object being monitored (such as a computer name), not the name of the alert or monitor, so filtering on it would not correctly isolate Alert1.
The MonitorObjectName property in the Operations Manager Integration Pack corresponds to the name of the monitor that generated the alert, which is Monitor1 in this scenario. Filtering on this property ensures the runbook only triggers for alerts originating from Monitor1 rather than any alert.
The Get Alert activity retrieves details about existing alerts on demand but does not continuously watch for new alerts and cannot serve as a runbook trigger.
The Monitor Alert activity in Orchestrator continuously polls Operations Manager for new or updated alerts and acts as the trigger point for the runbook. Configuring its trigger settings ties the runbook start to the appearance of matching alerts, making it the required starting activity for this automation flow.
The Name property in the alert filter refers to the alert rule or display name field in a different context and is not the correct filter property for matching a monitor by its configured name in this integration pack.
Concept tested: Orchestrator Monitor Alert activity with Operations Manager integration
Source: https://learn.microsoft.com/en-us/system-center/orchestrator/operations-manager-integration-pack?view=sc-orch-2019
Topics
Community Discussion
No community discussion yet for this question.