1V0-31.21 · Question #63
An administrator is troubleshooting an application via Workbench in vRealize Operations Manager and would like to only view root causes. Which option must the administrator select?
The correct answer is C. Hide Consequential Evidence. The Hide Consequential Evidence option is the only option that allows the administrator to view only root causes. When this option is selected, vRealize Operations Manager will hide objects that are consequential to the root cause of the problem. This can help the administrator…
Question
An administrator is troubleshooting an application via Workbench in vRealize Operations Manager and would like to only view root causes. Which option must the administrator select?
Options
- ASpecify Time Range
- BDecrease Object Scope
- CHide Consequential Evidence
- DInvestigate Property Changes
How the community answered
(17 responses)- A18% (3)
- B6% (1)
- C71% (12)
- D6% (1)
Explanation
The Hide Consequential Evidence option is the only option that allows the administrator to view only root causes. When this option is selected, vRealize Operations Manager will hide objects that are consequential to the root cause of the problem. This can help the administrator to focus on the root cause of the problem and to resolve it more quickly.
Topics
Community Discussion
7
Grigory K.Jun 26, 2026Answer is C, Hide Consequential Evidence. In vROps Workbench, when you pull up a symptom chain the tool shows you everything, root causes and all the downstream alerts that fired because of those root causes. That downstream stuff is called consequential evidence, and it is noise when all you care about is what actually started the problem. Selecting Hide Consequential Evidence strips those out and leaves you with just the root cause badges, which is exactly what you need when you are trying to pinpoint blame fast. The other options mess with scope or time window and do not filter the evidence type at all, so they do not get you there.
Dervla O.Jun 24, 2026Took me a second on this one because I almost went with D thinking property changes would explain causation, but then I remembered that Workbench layers evidence hierarchically, and toggling off the downstream noise is the whole point of C. Hide Consequential Evidence is what strips out the symptoms so you are only staring at what actually started the fire, which is exactly what you need when you are trying to stop chasing ghosts in a dependency chain.
Imani T.Jun 26, 2026I kept thinking it was B because narrowing the scope feels like the natural move when you are trying to cut through noise, but then it clicked that scope does not filter the type of evidence, it just changes what objects you are looking at. Hide Consequential Evidence is the one that actually strips out the downstream symptoms and leaves you staring at only the root causes, which is exactly what the question is asking for.
Mateus R.Jun 27, 2026Scope does the narrowing work Imani described, but the cleaner way to think of it is that Hide Consequential Evidence acts like a crime scene cleanup crew that removes all the secondary clues so you stop chasing symptoms and go straight to the thing that started the fire.
Brenda K.Jun 26, 2026Saw this one on my actual exam and almost burned two minutes on it before I caught myself, because "Decrease Object Scope" sounds plausible until you remember that Workbench is about filtering the symptom chain, not narrowing down objects. The move is C, Hide Consequential Evidence, because that toggle strips out the downstream symptoms and leaves you staring at root causes only, which is exactly what the question is asking.
Mateus R.Jun 26, 2026When you open Workbench and the symptom list is cluttered with downstream noise, narrowing the Object Scope is how you cut away the ripple effects and zero in on what actually started the chain reaction, because a tighter scope stops the tool from pulling in all the objects that got sick as a consequence of the real problem. That is why B is the move here, you are shrinking the blast radius of the investigation so only the originating object and its direct signals stay in frame.
Imani T.Jun 27, 2026Mateus, appreciate the detailed breakdown but the scope adjustment you are describing is what the Symptom Filter does, not the Object Scope setting. C is correct because narrowing the Symptom Filter is specifically what removes downstream noise from the list so you can isolate the root cause without hiding related objects that might still matter to your investigation.