A customer is using multiple vRealize Operations (vROps) instances and has one central development vROps instance for creating dashboards. The administrator is tasked to share the newly created…

Question

Options

• AGenerate a custom URL, set the expiration to "never expire", and import this URL into the other
• BUse the Embed option to import the HTML code into the other instances.
• CConnect the vROps instances together, and synchronize the dashboards.
• DExport the dashboard from the development instance, and import the dashboard into the other

• A
  2% (1)
• B
  2% (1)
• C
  3% (2)
• D
  93% (54)

Explanation

Exporting and importing dashboards (D) is the correct method because it packages the dashboard definition into a portable file that can be moved between vROps instances while preserving full editability - the receiving instance gets a native copy it owns completely.

Why the distractors fail:

• A - A custom URL shares a view of the dashboard, not the dashboard itself; it doesn't make the dashboard editable in another instance, and it depends on network connectivity to the source.
• B - The Embed option generates HTML for embedding dashboards in external web pages (portals, wikis), not for importing into other vROps instances.
• C - vROps instances don't have a built-in "connect and synchronize" feature for sharing dashboards between independent deployments; this capability doesn't exist as described.

Memory tip: Think of it like sharing a Word document - if you want someone to edit it, you send them the file (export/import), not a link to your screen (URL/embed).

No community discussion yet for this question.