Exam4Training

What is the cause of this issue?

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 returning to the troubleshooting workbench the following day, the administrator can see the Virtual Machine context as a recent search. Upon opening this object, though, the changes made the previous day are no longer visible.

What is the cause of this issue?
A . The product needs to be licensed with vRealize Operations Enterprise edition.
B . Changes made to scope, time, or potential evidence are not saved after logging out.
C . The administrator did not click the Save option when using the troubleshooting workbench.
D . The vRealize Operations instance has been restored from an earlier backup.

Answer: B

Explanation:

The cause of this issue is that changes made to scope, time, or potential evidence are not saved after logging out of the vRealize Operations user interface. The troubleshooting workbench feature allows the administrator to perform advanced troubleshooting tasks on an alert or an object by looking for potential evidences of a problem within a specific scope and time range. The administrator can modify the scope, time, or potential evidence in the active session, but these changes are not persistent and are lost when the administrator logs out or closes the browser1. The administrator can see the virtual machine context as a recent search because the recent searches are stored in the browser’s local storage, but the changes made to the troubleshooting workbench are not2.

The other options are not the cause of this issue. Option A is incorrect because the troubleshooting workbench feature is available in all editions of vRealize Operations, and the license edition does not affect the saving of the changes3. Option C is incorrect because there is no Save option when using the troubleshooting workbench, and the administrator cannot save the changes manually1. Option D is incorrect because restoring the vRealize Operations instance from an earlier backup would not affect the changes made to the troubleshooting workbench, as they are not stored in the vRealize Operations database or file system1.

References:

1: Troubleshooting Workbench Home Page

2: Where You Find the Troubleshooting Workbench

3: [vRealize Operations Manager Editions]

Latest 5V0-35.21 Dumps Valid Version with 76 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Exit mobile version