An online retail company needs its shopping cart application to be highly available. What three cloud management design decisions would give an optimal shopping experience? (Choose three.)

Question

Options

• ACreate a vRealize Operations metric chart for the application's CPU usage
• BCreate a vRealize Orchestrator workflow that remediates the issue by updating the CPU
• CConfigure the vRealize Operations alert to run a vRealize Orchestrator workflow when triggered
• DCreate a vRealize Operations alert that is triggered when the application's CPU usage exceeds a
• ECreate a vRealize Orchestrator workflow that emails an administrator to remediate the issue
• FConfigure the vRealize Operations alert to email an administrator to remediate the issue

• A
  13% (5)
• B
  80% (32)
• E
  3% (1)
• F
  5% (2)

Explanation

Options D, C, and B form a complete automated remediation pipeline: D sets up the CPU threshold alert (detection), C connects that alert to an automated workflow (trigger), and B creates the workflow that actually fixes the problem by adjusting CPU resources (remediation). Together, these three steps achieve self-healing infrastructure without human delay - critical for high availability.

Why the distractors fail:

• A (metric chart) is passive visualization only - it surfaces data but triggers nothing and fixes nothing.
• E and F (email an administrator) both require a human to wake up, log in, and manually intervene, introducing unacceptable latency for a shopping cart that needs to stay up 24/7.

Memory tip: Think of it as a three-act play - Alert → Trigger → Fix (D → C → B). Any option that puts a human in the loop (email) or stops at observation (chart) breaks the automation chain and fails the "optimal experience" bar. High availability = no waiting on humans.

No community discussion yet for this question.