County clinic operators store ISO images and VM templates in a shared inventory so new health-department guests can be deployed from one place. Which vSphere component is that inventory?
Select an answer to reveal the explanation.
Short Explanation
A content library is the clinic's shared supply closet for gold images and installer ISOs. NSX groups pick which VMs a firewall rule hits; they do not store templates. vSAN policies describe how disks are protected, not where ISOs live.
Full Explanation
County clinic operators who store ISO images and VM templates in a shared inventory so new health-department guests deploy from one place are using a content library—the vSphere store for templates and ISOs. A content library is the clinic’s shared supply closet for gold images and installer media used across the health department. An NSX inventory group used for Distributed Firewall membership selects which VMs a security rule applies to; it does not store ISO files or VM templates for deployment. A transport zone catalog of overlay network identifiers defines fabric span for segments, not a media repository. A vSAN storage policy that holds ISO files confuses policy-based storage placement with a content library; policies govern how disks are placed on vSAN, they are not the shared ISO/template inventory object. Exam caveat: content libraries can be local or subscribed/published across vCenters; associate depth is identifying the library as the template/ISO store rather than designing publish/subscribe topology. Operational check: in vCenter, open Content Libraries, confirm templates and ISOs used by the clinic are present, and deploy a test health-department VM from that library rather than from an NSX group, transport zone, or storage-policy object mistaken for a media catalog.