Official task 3.5 asks you to provision a UCS server from a template. Which platform API is the correct constructed answer?
Select an answer to reveal the explanation.
Short Explanation
Task 3.5’s numbered platform is UCS Manager—use its XML/SDK instantiate path. Intersight can deploy compute elsewhere, but that is not this task’s answer key.
Full Explanation
Official task 3.5 asks you to provision a UCS server from a template using the UCS Manager XML API (cookie session plus instantiate-from-template / SDK), not an Intersight server-profile POST. The numbered platform for that provision task is UCS Manager; constructed answers stay on aaaLogin, template DN, instantiate, associate, and commit.
Choosing Intersight server-profile POST because task 3.4 retrieve used Intersight fails by conflating adjacent objectives: retrieve on Intersight does not rewrite 3.5’s UCS Manager provision platform. ACI/APIC tenant and application-profile creates fail because ACI models network policy, not UCS blade service-profile identity from a UCS template. DNA Center Intent client-health GET fails entirely as a compute provision call—it is an assurance retrieve, not UCS provisioning.
Exam caveat: Intersight can manage or deploy compute in other scenarios, but that capability does not replace the UCS Manager instantiate path when the task statement names provision from a UCS template on UCS Manager.
Operational check: when practicing task 3.5, force the script to target the UCS Manager VIP only, assert the cookie comes from aaaLogin, and confirm the resulting object is an LsServer instance under the org DN—not an Intersight Moid—before calling the lab “done.”