An architect designed a vRealize Log Insight (vRLI) cluster for an organization with the following details: - The cluster has 3-nodes with 2 event forwarders sending logs to this cluster. - The vRLI…

Question

Options

• A
  1. Restore the forwarders
• B
  1. Restore the master node
• C
  1. Restore the worker nodes
• D
  1. Restore the master node

• A
  6% (3)
• B
  74% (40)
• C
  4% (2)
• D
  17% (9)

Explanation

Restoring the master node first (Option B) is correct because the vRLI master node is the authoritative controller of the cluster - it holds the configuration, manages cluster membership, and must be operational before any other component can join or function. Worker nodes (Option C is wrong) cannot register or synchronize without the master already running, making them second in the recovery sequence. Event forwarders (Option A is wrong) are external components that push logs into the cluster, so restoring them before the cluster itself exists means they have nowhere to deliver data. Option D, while also starting with the master node, represents an incorrect subsequent ordering of recovery steps (likely placing forwarders before worker nodes). The standard vRLI DR runbook sequence is: Master Node → Worker Nodes → Event Forwarders - always rebuild the foundation before the walls, and hang the pipes last.

Memory tip: Think "MWF" - Master, Workers, Forwarders - like a Monday–Wednesday–Friday schedule: you can't skip to Wednesday without Monday existing first.

No community discussion yet for this question.