An administrator has recently completed creating all the necessary Playbooks for day-to-day operations. The administrator is struggling to configure User Impersonation. What must the administrator do to ensure that their username is not associated with running Playbooks?

Prism Central can impersonate only identities that already exist in its local database. That database entry is created the first time a user—local or directory-based—logs in to Prism Central. Until that initial login occurs, the account cannot be selected in the “Run As” list and the playbook will continue to execute under the creator’s username. Therefore the administrator must ensure the intended local user has logged into Prism Central at least once.

A. Selecting the correct account is insufficient; Prism Central cannot display or use an account that has never logged in.
B. Impersonation supports both local and directory users; it is not restricted to domain accounts.
D. Runtime execution privileges regulate who can run or edit playbooks, not which username appears when actions run.

1. Nutanix Prism Central Administration Guide v6.5, “Playbooks → User Impersonation”, p. 814, Note: “The user to be impersonated must have logged on to Prism Central at least once.”

2. Nutanix Tech Note BP-2073, “Running Actions as Another User”, §3.2, bullet 1.

3. Nutanix University NCP-MCA Courseware, Module “Automation with X-Play”, slide 32 “User impersonation prerequisites”.