A township briefing lists a vSphere object that captures and applies consistent ESXi host settings, or a host lifecycle image, so every civic hypervisor matches. Which component is that?

A township briefing that lists a vSphere object capturing and applying consistent ESXi host settings, or a host lifecycle image so every civic hypervisor matches, is describing a vSphere host profile and/or a vSphere Lifecycle Manager (vLCM) image. Host profiles capture configuration for compliance remediation, and vLCM images standardize ESXi version and desired host state so every municipal hypervisor matches the approved baseline. An NSX uplink profile defines TEP teaming, VLAN, and MTU for host uplinks used by the NSX host switch; it is an NSX networking preparation object, not the general ESXi configuration or lifecycle image for the entire host. An NSX transport-node profile applies NSX host-switch and related transport settings when preparing hosts; it does not replace all host firmware or serve as the comprehensive vSphere host-configuration standard. A Distributed Firewall section hardens east-west traffic policy for workloads and does not image or configure the hypervisor kernel lifecycle. Exam caveat: NSX preparation profiles are easy distractors when the stem mentions "consistent host settings." At VCTA-NV depth, distinguish vSphere host configuration/lifecycle tools from NSX transport-node and uplink profiles that only cover NSX host-switch intent. Operational check: in vCenter, review the township host profile or vLCM image attached to the cluster, check compliance or remediation status for each ESXi host, and separately confirm in NSX Manager that transport-node and uplink profiles are applied for NSX preparation—proving civic host sameness and NSX readiness are both complete without treating one as the other.