A data-center civic ops tool must retrieve compute inventory summaries from Cisco Intersight SaaS. Which construction matches the official retrieve task?
Select an answer to reveal the explanation.
Short Explanation
Retrieve means GET a resource class—like pulling a labeled binder of PhysicalSummaries—not writing policies or dropping into UCS Manager XML login.
Full Explanation
Retrieving compute inventory summaries from Cisco Intersight SaaS follows a read of resource classes over the Intersight API. The construction that matches the official retrieve task is GET /api/v1/<class> on intersight.com—for example compute/PhysicalSummaries—to list summary inventory objects. GET on the class path is how unattended ops tools pull labeled inventory without performing write-side provisioning.
POST or PATCH a policy class to write a new server profile as the “retrieve” method fails because those verbs mutate policy/profile state; writing is not retrieve. Sending UCS Manager XML aaaLogin and treating the cookie as Intersight retrieve fails product boundary: UCS Manager XML APIs are not the Intersight SaaS REST retrieve path. Deploying an Intersight server profile and reading only the deploy job fails inventory retrieve: deploy jobs report provisioning progress, not the PhysicalSummaries inventory class listing.
Exam caveat: Intersight paths are class-oriented under /api/v1/; memorizing one example class (PhysicalSummaries) helps, but filters/select query params are often needed for large tenants.
Operational check: authenticate, GET compute/PhysicalSummaries (with a small top/limit if available), and verify returned managed object type/name fields match expected civic DC inventory before scheduling nightly pulls.