After a Prism Central upgrade, IAM authentication settings may require reconfiguration.
* Option D (Log in with a local admin account) is correct:
* If IAM authentication fails, thelocal admin account must be usedto check domain settings.
* Option A (Ping the Domain Controller) is incorrect:
* Network connectivity is important, but theissue is likely related to IAM settings, not network reachability.
* Option B (Check firewall port 9441) is incorrect:
* Port 9441 is used forSSO authentication, butport issues usually result in login delays, not complete failures.
* Option C (Validate signing certificate) is incorrect:
* While certificates can cause issues,local admin login should always work.
References:
Nutanix KB #Troubleshooting IAM Login Issues After a Prism Central Upgrade Nutanix Documentation #Managing User Authentication and IAM Integration

In Nutanix AHV-based clusters, when you want to ensure that a specific VM (e.g., a critical VM like a domain controller) is powered on before other VMs during a host startup or failover scenario, you use the Agent VM configuration setting.
Here's the exact explanation from the Nutanix ECA course:
"Agent VMs are special VMs that are automatically powered on before other user VMs during host startup or recovery. This ensures that critical VMs, such as those that provide essential services, are always available first." In contrast:
#Recovery Plan (A) - This is used in the context of DR and failover, typically with Nutanix Leap.
#Host Affinity (B) - Host affinity rules control placement policies of VMs but not startup priority.
#High Availability (C) - HA ensures VMs are restarted on surviving hosts but does not control startup order.
Therefore, setting the VM as an Agent VM guarantees that it is powered on before the other VMs during host start-up. Let me know if you'd like steps on how to configure an Agent VM within Prism Central or Prism Element!

Before performing any LCM (Life Cycle Manager) updates on a Nutanix cluster, it is essential to ensure that the AOS (Acropolis Operating System) is updated to the required or recommended version. AOS updates provide foundational enhancements, security patches, and compatibility improvements, which are critical for the successful execution of LCM updates.
From theNutanix Enterprise Cloud Administration (ECA)course materials:
"LCM updates depend on the underlying AOS version. Before proceeding with any hardware or software updates through LCM, administrators must ensure that the cluster is running a supported AOS version. This step ensures compatibility and prevents issues that can arise from dependencies between AOS and the update components." Additionally:
"AOS upgrades should be performed first to bring the cluster to a version that supports the desired LCM updates for components like BIOS, firmware, and hypervisors. This aligns the management stack with the latest features and security enhancements." Therefore, updating AOS before performing LCM updates is a mandatory prerequisite to ensure stability and supportability for the entire cluster lifecycle management process.