Q: 3
An administrator is responsible for the management of a VMware Cloud Foundation (VCF)
environment and has been tasked with creating a new Organization in VCF Automation. The
customer previously upgraded from VCF 5.2 and this is the first new Organization since their
upgrade.
The following requirements have been provided for the additional Organization:
Onboard existing Virtual Machines (VM) for management through VCF Automation.
Use third-party integrations, including Tanzu Salt and Active Directory.
Deploy to Native Public Cloud (NPC) endpoints.
What action should the administrator take to complete the objective?
Options
Discussion
B . "All Applications" org type is what actually delivers both public cloud endpoint support and the wide third-party integrations after upgrading from 5.2, but if they'd limited this org creation to API-only access (not portal), C could become valid in edge cases. Not likely here though.
Its B. Only "All Applications" orgs in the Provider Management Portal allow both public cloud endpoints and those third-party tools (Tanzu Salt, AD). Option A is a trap, too limited for the requirements. Not 100% sure if C could work in weird API-only scenarios but feels less likely here. Correct me if you disagree.
I don’t think it should be A here. If you use the "VM Applications" org type (option A), it’s really just basic VM onboarding and doesn’t support all the integrations or NPC requirements. Option C is tempting because of the API mention, but unless automation at scale is explicitly required, Provider Management Portal (B) is more appropriate for these advanced features. Pretty sure B is best but open to other takes if I missed something tricky in post-5.2 behavior.
B tbh
B
B is the one. With those requirements (third-party integrations plus NPC endpoints), you need the "All Applications" Org in Provider Management Portal. A won't support everything and C is usually if automation via API is specifically required. I think B but open to corrections if I missed something in newer docs.
B is right here. Only the "All Applications" org type in the Provider Management Portal lets you use both integrations and NPC endpoints after 5.2. "VM Applications" just won't cover everything asked. Pretty sure about B, anyone see a catch?
B , A looks tempting but "VM Applications" orgs miss out on those integrations after 5.2.
I don’t think it's C. B. "All Applications" via the Provider Management Portal is what supports both requirements here.
Probably B. But in edge cases where portal access isn’t available and they use API-only, C could technically work.
Be respectful. No spam.
