Q: 1
Existing environment:
3 vSphere clusters, 5 hosts each.
Networking = vDS.
Storage = NFSv3.
Managed by single vCenter.
Architect decides to create a new VCF fleet with a single VCF instance.
What design implication should be documented?
Options
Discussion
Option B, not D. Pretty sure the real risk is the vCenter VM causing a management loop if it stays on hosts that VCF will take over. D is tempting but VCF doesn’t force baseline conversion during fleet creation.
Option B saw a similar question in exam reports and that's what was picked.
B
Probably B makes sense since if the vCenter VM stays on any host planned for VCF management, there’s a risk of circular dependency and deployment failure. That’s a key design issue to document before building out a new VCF fleet from an existing environment. Not totally sure if configs always force this, but it's the safest choice here. Agree?
C/D? I’ve seen NFS setups where vSAN gets applied by mistake, so clusters moving to vSAN config could also be a concern.
Had something like this in a mock, pretty sure it's B.
B, not A. Migrating vCenter off the cluster is needed here. Pretty sure that's the key design point.
B , the key point is avoiding a circular dependency by moving the vCenter VM before building the fleet. Seen this in official guides and practice tests too. If anyone's got something newer contradicting that, let me know.
the reference for this is pointing v5.2 documentation when this exam is for v9. This is outdated information. version 9 does not have this requirement. The answer is A.
B tbh. If you don't move the vCenter VM off, SDDC Manager can hit a deadlock during VCF bring-up. Seen this gotcha in some exam reports, easy to overlook unless you read the VCF prerequisites closely.
Be respectful. No spam.
