Exam 3V0-12.26 Topic 1 Question 9 Discussion

A and E best satisfy the multi-instance scale requirement while keeping the identity-management footprint as small as possible.
A VCF Identity Broker should be associated with the management infrastructure , not deployed independently in workload domains. Broadcom documentation shows VCF Identity Broker as part of the VCF management-plane architecture and identifies the management domain as the normal installation location for the identity service. ( VMware Blogs ) The scale requirement determines the number of Identity Broker deployments. Broadcom states that an external/appliance VCF Identity Broker is intended for multi-instance fleets and is recommended to support up to five VCF instances . ( VMware Blogs ) With seven VCF instances , one broker would exceed that recommended scale boundary, while seven embedded brokers would create unnecessary compute footprint and operational overhead. The minimum practical topology is therefore two VCF Identity Broker deployments , distributed through the VCF Management Services architecture.
VCF 9.1 further integrates identity services with the broader VCF Management Services platform, and Broadcom requires the Identity Broker to reside on the same management network as those services.
B is incorrect because workload domains are not the preferred hosting boundary for centralized fleet identity.
C creates the largest footprint. D is insufficient by itself because a single Identity Broker does not meet the recommended scale for seven VCF instances.
Study Guide References/Topics: VCF Identity Broker; Fleet-Level SSO; VCF Management Services; Management Domain Placement; Multi-Instance Identity Design; Identity Broker Scale and Footprint.