Free VMware 2V0-16.25 Actual Exam Questions - Question 2 Discussion
Operations for Linux Guest Operating Systems. For security reasons a non-root user needs to be used
and all required steps for the Guest OS have already been completed.
What are the two steps the administrator needs to take? (Choose two.)
E imo, since non-root user needs sudo enabled in the Service Discovery instance.
B imo, you gotta enable Service Discovery in vCenter to start with, and then E makes sense since the non-root user needs sudo rights on the Service Discovery instance. A looks off since sudo is more relevant locally.
A imo, activating Use Sudo in the vCenter instance (A) doesn't make much sense since the sudo rights are needed on the Service Discovery side where the guest OS commands run. Plus, you definitely need to enable Service Discovery on the vCenter instance itself (B), so that part is clear. E fits better because it directly relates to giving the non-root user proper privileges where it matters. C and D seem off since NSX isn’t involved in this process and deactivating sudo contradicts the need for elevated rights. So B and E feel like the right picks for this scenario.
It’s B and E. Service Discovery has to be enabled on the vCenter instance, and since the user isn’t root, sudo must be activated on the Service Discovery instance itself for proper permissions.
Probably B and E; enable Service Discovery on vCenter and sudo on the Service Discovery instance.
B, E. You need to enable Service Discovery on the vCenter instance itself, and since it’s a non-root user setup, sudo must be activated in the Service Discovery instance, not just the vCenter one.
Probably B and E since service discovery must be enabled plus sudo in the Service Discovery instance.
Maybe B and E. You need to activate Service Discovery in vCenter first and then enable Use Sudo in the Service Discovery instance to allow non-root users to execute commands securely.
Maybe B and A, since Use Sudo should be enabled in vCenter when using non-root accounts.
B, E. Since the question mentions a non-root user and everything on the Guest OS side is done, you definitely need to enable Service Discovery in the vCenter instance (B). Then, enabling Use Sudo in the Service Discovery instance (E) is necessary so that the non-root user can execute commands with elevated privileges without giving full root access. Activating Use Sudo in vCenter (A) or NSX (C) doesn’t fit here since the focus is on the Service Discovery component itself. Also, D contradicts the need for sudo with a non-root user.
Gotta go with B and E here. Activating Service Discovery in the vCenter and enabling Use Sudo in the Service Discovery instance makes the most sense for non-root user setup.