Which UCS Manager method creates named service-profile instances from a given template?
Select an answer to reveal the explanation.
Short Explanation
Instantiate-from-template is the stamp press: template DN in, named service profiles out. Reading with configResolveClass only looks—it never presses.
Full Explanation
Creating named service-profile instances from a given UCS template uses lsInstantiateNNamedTemplate / lsInstantiateTemplate (or the SDK wrapper that issues the same method). The call takes the template DN, target organization, and the new profile name(s), producing logical LsServer instances the city can later associate to hardware.
configResolveClass alone fails because resolve is a read/query path: it can locate the template but does not create new named profiles. Logging in a second time with the profile name instead of calling instantiate fails by confusing authentication with provisioning—aaaLogin establishes a session; it does not stamp instances from a template. An Intersight POST to compute/Blade that bypasses UCS Manager fails because that is a different platform and is not the UCS Manager instantiate-from-template method the task expects.
Exam caveat: instantiate creates logical profiles; it does not by itself place those profiles on blades—association remains a separate required step in a complete provision story.
Operational check: after instantiate, resolve the new profile DN under the target org, confirm the name matches the civic naming standard (library/transit/parks prefixes), and only then proceed to associate so empty logical profiles are not mistaken for running servers.