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 or maybe C? Pretty sure B is right because "All Applications" orgs are the only ones that support both third-party tie-ins and public cloud endpoints after the upgrade, but if VCF API boundaries ever changed, C could sneak in. Anyone else notice this in recent versions?
This depends on needing third-party integrations and NPC, which only works with All Applications orgs via the Provider Management Portal. B
B imo. Only the 'All Applications' org type in the Provider Management Portal supports both third-party integrations and NPC deployment. I ran into a similar requirement after a VCF upgrade and VM Applications is just too limited for this.
Be respectful. No spam.
