CSA domain - 20% of the exam

Self Service & Automation

Self Service & Automation is 20% of the CSA exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

68
Practice questions
4
Objectives
22
Medium
46
Hard

Where people go wrong

  • Letting an inclusion list outrank an exclusion list

    The wrong answers settle a conflict by the wrong rule: the inclusion list runs last, the later list wins, the entries average out, or the most specific attribute decides. User criteria are not ranked by sequence or specificity. A user who matches both Can Read and Cannot Read on a knowledge base is denied, and a requester who matches both Available For and Not Available For on a catalog item does not see it. The exclusion list is the stronger one.

    See it in a sample question
  • Using roles or categories to govern knowledge access

    The wrong answers reach for a role, an access control rule, a category or the knowledge admin role. The audience of a knowledge base is set by user criteria records on its Can Read list, and a separate Can Contribute list decides who may author. Categories organise browsing and hide nothing, and knowledge admin gives management of every knowledge base. Adding experts to Can Read leaves their authoring unchanged, and contractors matching no Can Read criteria cannot see the base.

    See it in a sample question
  • Treating a catalog item as a direct record insert

    When a submission must create a record on a table with no request and no requested item, the wrong answers offer a catalog item, an order guide or a flow. Ordering a catalog item always opens a request and a requested item first, and an order guide only wraps catalog items. A record producer is bound to a target table, inserts the record directly, and maps each variable to a field such as Short description or Category.

    See it in a sample question
  • Collapsing the request, requested item and catalog task hierarchy

    The wrong answers merge levels or move them: one requested item for several items, one request per item, or catalog tasks hung directly under the request. A submission is one request. Each ordered catalog item becomes its own requested item carrying its variable answers, and the fulfilment of that item generates catalog tasks beneath that requested item. Two items with two tasks each give one request, two requested items and four catalog tasks.

    See it in a sample question
  • Using a business rule or classic workflow where a flow must wait

    The wrong answers use a business rule or the classic workflow engine for automation that spans approvals, timers and integration calls. A business rule runs to completion in one transaction, so it cannot pause for a human approval or a timer. Classic workflow is the legacy engine. A flow in Workflow Studio holds an approval, a timer and a vendor spoke action in one configured sequence, without hand written script.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleSelf Service & Automationmedium

A knowledge base lists user criteria matching all permanent employees on its Can Read list, and separate user criteria matching contractors on its Cannot Read list. A contractor who is also a permanent employee record holder matches both sets of criteria. What determines the outcome for that user?

  • AThe user gains read access, because a matching entry on the Can Read list is evaluated after the exclusion list
  • BThe user gains read access, because user criteria matching is additive and any single match is sufficient
  • CThe user is denied read access, because a match on the Cannot Read list takes precedence over a match on Can Read Correct
  • DThe user gains read access, because the criteria are compared and the one matching more attributes takes effect
On a knowledge base, a match on the Cannot Read or Cannot Contribute list overrides any matching entry on the corresponding inclusion list. Knowledge bases carry paired lists: Can Read with Cannot Read, and Can Contribute with Cannot Contribute. The inclusion lists are additive, so matching any one entry admits the user, but the exclusion lists are checked as an override. A user who matches both is therefore excluded, which is what makes the negative lists useful for carving a group out of a broad audience.

Why A is wrong: It is tempting to assume the inclusion list runs last and therefore wins, but the exclusion list is what settles a conflict, so access is denied rather than granted.

Why B is wrong: Multiple criteria on one list are indeed additive, so this reasoning is half right, yet it ignores that the Cannot Read list exists precisely to remove users the inclusion list would otherwise admit.

Why C is correct: The exclusion lists are designed to override the inclusion lists, so any user matching Cannot Read is kept out of the knowledge base regardless of another match.

Why D is wrong: Specificity decides the winner among access control rules on some platforms, which makes this feel familiar, but knowledge user criteria are not scored against each other by attribute count.

Free sampleSelf Service & Automationmedium

A knowledge base holds articles that only staff in the Finance department should be able to open, and those staff hold no roles beyond the ones every logged in user receives. Which mechanism governs who is allowed to read the articles in that knowledge base?

  • AA user criteria record matching the Finance department, added to the Can Read list of that knowledge base Correct
  • BA role added to the knowledge base record, granted to each Finance user through their group membership
  • CA read access control rule on the knowledge article table whose condition matches the department of the current user
  • DA category inside the knowledge base named Finance, with the articles filed under it for the department
Knowledge base read audiences are declared with user criteria on the Can Read list, not with roles, access control rules or categories. User criteria are reusable records that describe a set of users by attributes such as department, group, location or company. A knowledge base points at them from its Can Read and Can Contribute lists, and the platform evaluates the current user against those criteria when deciding whether the knowledge base and its articles are available. That is why an audience defined by department needs no new role.

Why A is correct: User criteria evaluate attributes such as department, group, location, company and role, and the Can Read list on a knowledge base is exactly where read audience is declared.

Why B is wrong: Roles are the familiar way to gate most platform features, so reaching for one is tempting, but knowledge read access is evaluated through user criteria rather than a role field on the knowledge base.

Why C is wrong: Access control rules do protect the table generally, but the per knowledge base audience for articles is decided by user criteria, so writing a rule here duplicates and fights the supported mechanism.

Why D is wrong: Categories organise articles for browsing and searching, which feels like structure equals security, but a category carries no audience and hides nothing from anyone.

Free sampleSelf Service & Automationhard

A team needs a self service form that a requester completes so that a new enquiry is logged straight onto a custom task table, with no fulfilment stage, no approval and no entry in the request queue. Which Service Catalog building block produces that outcome, and what does a submission create?

  • AA record producer, which writes a record straight onto the target table it is configured against and raises no requested item. Correct
  • BA catalog item, which writes a record onto the target table directly and raises no requested item for the fulfilment queue.
  • CAn order guide, which gathers the answers once and writes them onto the target table without generating any fulfilment task.
  • DA variable set, which carries the questions and writes the collected answers onto the target table when the requester submits.
Distinguish a record producer, which inserts a record directly onto a target table, from a catalog item, which always generates a requested item. The distinction is what the submission writes. A catalog item is an orderable product, so submitting it creates a request with a requested item that fulfilment works through. A record producer is a front end for a table: its variables are mapped onto fields of the target table and submission inserts one record there, bypassing the request structure entirely.

Why A is correct: A record producer presents catalog style questions but inserts the submitted answers directly onto its configured target table, so no request or requested item is created and there is no fulfilment stage to track.

Why B is wrong: Tempting because a catalog item shows the same variable driven form, but ordering one always generates a requested item under a request, which is precisely the queue entry the requirement rules out.

Why C is wrong: An order guide does collect answers once, which makes it look like a lightweight form, but its purpose is to submit one or more catalog items together, so it produces a request rather than a direct record insert.

Why D is wrong: A variable set is a reusable group of questions only; it has no submit behaviour and no target table of its own, so it cannot create anything on its own without a catalog item or record producer to host it.

Free sampleSelf Service & Automationhard

A new starter order guide bundles three catalog items: a laptop, a mobile handset and a building pass. A hiring manager works through the order guide once, keeps all three items, and submits. Each of the three items carries its own fulfilment process that raises work for a different group. Which set of records does the submission produce?

  • AOne request, one requested item carrying all three items, and one catalog task for each fulfilment group involved.
  • BThree requests, each holding one requested item, linked to one another by the order guide that produced them.
  • COne request holding three requested items, with each requested item generating its own catalog tasks from its fulfilment. Correct
  • DOne request holding three catalog tasks directly, with requested items created only when a fulfiller accepts work.
Recognise that an order guide produces one request containing a requested item per ordered item, each raising its own catalog tasks. The catalog record hierarchy has three levels. The request is the submission and the approval container, a requested item represents one ordered catalog item and carries that item's variables and fulfilment, and catalog tasks are the units of work created by that fulfilment. An order guide changes only how items are gathered before submission, so the hierarchy underneath is unchanged.

Why A is wrong: Tempting because a single submission feels like a single line of work, but an order guide does not merge items into one requested item, and fulfilment is driven per requested item rather than per group.

Why B is wrong: Plausible if you assume each item is ordered separately, but the point of an order guide is one submission and one request, so splitting into three requests would lose the single approval and tracking record.

Why C is correct: An order guide bundles several items into a single request, and each ordered item becomes its own requested item that runs its own fulfilment and raises its own catalog tasks.

Why D is wrong: This skips a level of the hierarchy, since catalog tasks are children of a requested item rather than of the request, and requested items are created at submission rather than on acceptance.

Free sampleSelf Service & Automationhard

A process must collect two approvals, then send a request to a supported external system through a vendor supplied integration, and it must remain readable and editable by administrators who do not script. Which build approach fits the current platform guidance?

  • ABuild a flow in Flow Designer within Workflow Studio, using a vendor spoke action for the external call. Correct
  • BBuild a classic workflow, since only that engine offers approval activities alongside external callouts.
  • CWrite a before business rule that runs the approval logic and calls the external system synchronously.
  • DWrite a scheduled script execution that polls the table and issues the approvals and the external call.
Choose a flow when a process needs approvals, waits and integration steps that non scripting administrators must be able to read and change. Flows persist across transactions, so an approval that waits for days does not hold a database save open, and each step is declared rather than coded. Business rules run inside the save transaction and classic workflow is the superseded engine, so neither meets the durability and maintainability requirement.

Why A is correct: Correct, because Flow Designer is the current authoring environment for approvals and integration steps, and spoke actions expose the external call without scripting.

Why B is wrong: Tempting because classic workflows genuinely do offer approval activities, but they are the legacy engine and the claim of exclusivity is wrong, since flows provide approvals and spoke actions too.

Why C is wrong: Tempting because a business rule reacts to the record change, but approvals span days and a before rule runs inside the save transaction, so it can neither wait nor stay readable to non scripters.

Why D is wrong: Tempting because polling would eventually pick the records up, but it adds latency, hides the logic in script and duplicates orchestration the flow engine already provides.

Other domains in this exam

See also the CSA cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ServiceNow. Original, blueprint-aligned practice material only.