An administrator is tasked to configure Service Discovery in VMware Cloud Foundation (VCF) Operations for Linux Guest Operating Systems. For security reasons a non-root user needs to be used and all…

Question

Options

• AActivate Use Sudo in the vCenter instance.
• BActivate Service Discovery in the required VCF Operations vCenter instance.
• CActivate Service Discovery in the required VCF Operations NSX instance.
• DDeactivate Use Sudo in the Service Discovery instance.
• EActivate Use Sudo in the Service Discovery instance.

• A
  15% (5)
• B
  74% (25)
• C
  3% (1)
• D
  9% (3)

Explanation

Configuring Service Discovery for Linux Guest OS with a non-root user requires two administrator-side steps: enabling Service Discovery at the vCenter instance level (B), which is where guest VMs reside and where the feature is toggled on in VCF Operations, and activating "Use Sudo" within that Service Discovery instance (E), which grants the non-root credential the elevated privileges needed to inspect running services on Linux.

Why the distractors are wrong:

• A is wrong because "Use Sudo" is a setting on the Service Discovery instance, not the vCenter instance - mixing up the configuration target.
• C is wrong because Guest OS Service Discovery is vCenter-driven, not NSX-driven; NSX handles network-layer discovery, not in-guest process inspection.
• D is the opposite of what's needed - deactivating sudo would prevent the non-root user from running the privileged commands required for discovery.

Memory tip: Think "Boot the feature at vCenter, Elevate with sudo for non-root" - B turns it on where your VMs live, E makes the unprivileged account work by borrowing root-level access via sudo.

No community discussion yet for this question.