A vRealize Operations Manager administrator has the following requirement: Whenever any object is selected in Widget-1 of Dashboard-A, then ONLY Widget-2 of Dashboard-B should be populated with the…

Question

Options

• AKeep Refresh Content Off
• BKeep Self-Provider Mode Off
• CKeep Refresh Content ON
• DKeep Self-Provider Mode ON

• A
  12% (5)
• B
  5% (2)
• C
  10% (4)
• D
  74% (31)

Explanation

Option D is correct because in vRealize Operations Manager, setting Widget-2's Self-Provider Mode to ON enables it to act as a receiver that populates its content based on an object selected in another widget - even across dashboards - making it respond exclusively to Widget-1's selection in Dashboard-A. Without this mode enabled, Widget-2 has no mechanism to accept the cross-dashboard interaction signal and will not dynamically populate based on Widget-1's context.

Why the distractors are wrong:

• Option B (Self-Provider OFF) is the common trap: with Self-Provider OFF, Widget-2 ignores external selections and falls back to static or default content, meaning it won't respond to Widget-1 at all.
• Options A and C (Refresh Content) control whether the widget auto-refreshes its data on a timer - this has nothing to do with widget-to-widget interaction or cross-dashboard object selection.

Memory tip: Think of Self-Provider Mode as a "listening switch." When it's ON, Widget-2 is listening for an object to be handed to it from another widget. When it's OFF, Widget-2 is deaf to external selections and ignores them. For cross-dashboard driven widgets, always turn the listener ON.

No community discussion yet for this question.