CSA - Self Service & Automation (20% of the exam) - Section 4
Service Catalog
Catalog items, record producers and order guides, categories, variables and variable sets, the request, requested item and catalog task record hierarchy, fulfilment through flows or workflows, and user criteria that control what a requester can see. Items separate these building blocks and their outputs.
Service CatalogRecord producersOrder guides
Practice question for this objective
lock_openFree sampleSelf Service & Automationhard
A requester submits one order containing two different catalog items, and the fulfilment process configured on each item raises two separate units of work for two different fulfilment groups. Which record structure does the platform produce for that submission?
ATwo requests, each holding one requested item, with two catalog tasks generated beneath each of those requested items.
BOne request holding one requested item that names both products, with four catalog tasks generated beneath that requested item.
CTwo requests, each holding two requested items, with one catalog task generated beneath every one of those requested items.
DOne request holding two requested items, with two catalog tasks generated beneath each of those two requested items.check_circle Correct
Map a catalog submission onto the three level record hierarchy of request, requested item per ordered item, and catalog tasks per requested item. The Service Catalog hierarchy has one level per concern. The request records the submission and the requester, one requested item records each ordered item with its own variable answers and its own fulfilment state, and catalog tasks record the individual units of work that an item's flow or workflow generates for fulfilment groups.
Why A is wrong: Tempting because the two items go to different groups, which suggests separate orders, but a single submission produces a single request no matter how many distinct items it contains.
Why B is wrong: This collapses the middle layer, which is a common misreading, but a requested item represents one ordered item and its variable answers, so two ordered items cannot share one requested item.
Why C is wrong: The task count matches the work described, which makes it look right at a glance, but it duplicates both the request and the requested items and misplaces where the two units of work belong.
Why D is correct: The submission itself is the request, each ordered item becomes its own requested item carrying that item's variable answers, and each item's fulfilment process generates its own catalog tasks under its requested item.
Answers that look right on this material and are not. Each one is a distractor from a different question in the CSA bank for this domain.
One request and one requested item are created, because the request groups both catalog items into a single fulfilment unit for the teams involved.
errorWhy it is wrong: Tempting because the requester made one submission and sees one request number, but each ordered catalog item gets its own requested item beneath that request.
One request and one requested item, with the three included items recorded as variables on that single requested item.
errorWhy it is wrong: Tempting because the requester submitted once, but the requested item is the unit of fulfilment for one catalog item, so collapsing three items into one would leave them without separate approvals.
She sees the item, because Available For criteria are evaluated first and a match there ends the visibility evaluation.
errorWhy it is wrong: Tempting because it mirrors first match wins behaviour elsewhere on the platform, but catalog visibility evaluates the denial list against the user regardless of an earlier grant.