An administrator has created a custom dashboard for a project to provide visibility into total cost of ownership and application performance. The data in the dashboard should be driven from a single…

Question

Options

• AConfigure dashboard sharing
• BEnable the Refresh Content option
• CConfigure the object relationship widgets
• DConfigure the interactions between widgets

• A
  6% (2)
• B
  3% (1)
• C
  11% (4)
• D
  80% (28)

Explanation

Configuring widget interactions is the correct solution because, in platforms like VMware vRealize Operations (vROps), widgets on a dashboard are independent by default - clicking an object in one widget does not automatically drive or filter data in other widgets unless you explicitly wire them together. The Interactions configuration tells the dashboard which widget acts as the "provider" (the VM list) and which widgets are "receivers" that update based on the selection.

Why the distractors are wrong:

• A (Dashboard sharing): Sharing controls who can view the dashboard, not how widgets communicate with each other - irrelevant to the filtering problem.
• B (Refresh Content): Refreshing pulls the latest data from the source, but it doesn't link the selection state of one widget to another.
• C (Object relationship widgets): These display topology/relationships between objects (e.g., VM → Host → Cluster), not the interaction between dashboard widgets.

Memory tip: Think of widget interactions as "wiring" - you've built the widgets (appliances), but they won't talk to each other until you run the wires between them. If clicking one widget doesn't update others, the wires (interactions) are missing.

No community discussion yet for this question.