A development team would like to ensure that provisioned machines automatically update a customer asset database (CMDB) resource that is managed by the domain administration team. All updates to the…

Question

Options

• ADesign an Event Broker event that triggers when the workflow is run and automatically runs a
• BInclude an email notification workflow in the XaaS workflow that sends an update email to the
• CConfigure an approval policy with a post-approval level that notifies the domain administration
• DInclude an email notification and user input workflow in the XaaS workflow that applies to domain

• A
  10% (4)
• B
  80% (33)
• C
  7% (3)
• D
  2% (1)

Explanation

Option B correctly satisfies both remaining requirements - automatic CMDB updates AND team notification - by embedding an email notification directly inside the existing XaaS workflow. Since the workflow already handles the CMDB interaction, adding a notification step within it ensures domain admins are always informed whenever the workflow runs, with no additional infrastructure needed.

Why the distractors are wrong:

• A (Event Broker): Introduces a separate, external event-driven mechanism when the requirement can be handled more simply inside the existing workflow. It's an over-engineered solution for a notification need.
• C (Approval policy with post-approval notification): Approval policies imply human gating before the action completes. The question requires automatic updates - adding an approval step breaks that automation requirement.
• D (Email + user input workflow): User input means the process is no longer automatic. Requiring a human to provide input contradicts the "automatically update" requirement.

Memory tip: Look for the answer that keeps automation intact while adding communication - if the question says "automatically" and an option adds approvals or user input, eliminate it immediately. Embedding notification inside an existing workflow is almost always preferred over external triggers when the goal is simplicity and reliability.

No community discussion yet for this question.