When a municipal UCS script provisions “given a template,” which object is that template?
Select an answer to reveal the explanation.
Short Explanation
The “template” is a service-profile template—an LsServer under an org DN—like a city building blueprint filed under the right department folder, not a raw blade or an Intersight profile.
Full Explanation
In the official “provision given a template” UCS flow, the template is a service-profile template—an LsServer managed object with a template type—addressed under an organization DN such as org-root/ls-<name>. That object is the blueprint municipal scripts clone into named service-profile instances; locating the correct template MO under the right org is part of the constructed answer.
Treating the template as a bare-metal blade chassis entry created with a direct POST to the FI fails because blades are hardware targets, not the service-profile template object the instantiate methods clone. An Intersight server profile under an organization Moid fails by platform: Intersight profiles are a different control plane than UCS Manager XML templates. A DNA Center network device credential template fails by domain mix-up: wireless onboarding credentials are unrelated to UCS LsServer templates.
Exam caveat: multiple orgs can hold similarly named templates—org-root versus a child org changes the DN; resolving the wrong org’s LsServer instantiates the wrong identity for city workloads.
Operational check: resolve the template DN under the intended org before instantiate, confirm the object is a template-type LsServer (not an already bound instance), and record the DN in the job log so auditors can see which municipal blueprint produced each profile.