An administrator has been using the troubleshooting workbench feature to identify an issue with a virtual machine and configured the specified time range and scope in the active session. When…

Question

Options

• AThe product needs to be licensed with vRealize Operations Enterprise edition.
• BChanges made to scope, time, or potential evidence are not saved after logging out.
• CThe administrator did not click the Save option when using the troubleshooting workbench.
• DThe vRealize Operations instance has been restored from an earlier backup.

• A
  8% (4)
• B
  86% (44)
• C
  2% (1)
• D
  4% (2)

Explanation

Option B is correct because the vRealize Operations troubleshooting workbench is designed as a session-based, stateless tool - any scope, time range, or evidence configurations are held only for the duration of the active session and are discarded upon logout, by design.

Why the distractors are wrong:

• A is incorrect because the troubleshooting workbench feature is not gated behind an Enterprise license tier; licensing does not affect session persistence behavior.
• C is incorrect because the troubleshooting workbench has no "Save" button or explicit save mechanism for session state - this option describes a feature that doesn't exist.
• D is incorrect because a backup restoration would affect the entire instance and all data, not just one administrator's session configuration, and there is no indication of a broader system restore.

Memory tip: Think of the troubleshooting workbench like a browser's private/incognito window - everything you configure exists only while you're in that session. When you close it (log out), the slate is wiped clean. "Workbench, not workspace" - it's a temporary work surface, not persistent storage.

No community discussion yet for this question.