CSA domain - 20% of the exam

Configuring Applications for Collaboration

Configuring Applications for Collaboration is 20% of the CSA exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

67
Practice questions
9
Objectives
61
Medium
6
Hard

Where people go wrong

  • Adding a table, field or script for a layout need

    For a layout need, the wrong answers add structure or code: a second incident table for a shorter form, a read only field holding instruction text, a UI policy hiding surplus fields, or a client script showing a message. A second table splits the incident data, and a read only field adds a column that reaches lists and exports. A form view with a view rule gives one set of records a second layout, and a form annotation places static text beside a section without storing anything.

    See it in a sample question
  • Mixing up Save, Update, Insert and Insert and Stay

    The wrong answers swap the four form actions because each one commits the on-screen values. Save and Update write back to the record already open: Save keeps that record on the form, while Update returns to the previous list. Insert and Insert and Stay create a second record and leave the original untouched: Insert returns to the list, while Insert and Stay keeps the new record on the form.

    See it in a sample question
  • Confusing a template with a default value

    The wrong answers treat a template as automatic, or a default value as something a user opts into. A dictionary default value fills every new record with no action by the user, so it suits a value that must always be present. A template is applied deliberately, only to the records that need it, and it overwrites the fields it names, including a value already held. Its values reach the database only when the form is saved.

    See it in a sample question
  • Treating a freeform board lane as a field value

    The wrong answers expect lanes on a freeform or flexible Visual Task Board to behave like values of a field. Those lanes are labels the owner types, so dragging a card writes nothing to State or Change state, and records that match a condition are not pulled in automatically. A guided board is built on a table with a filter, maps its lanes to a field, adds matching records on its own, and writes the lane value back on a drag.

    See it in a sample question
  • Routing or creating records with the wrong tool

    The wrong answers route incidents or create follow-up records with tools built for other jobs: a client script, a UI policy, a personalised default, a service level agreement or an update set. An assignment rule, or an assignment data lookup rule, sets Assignment group on the server as the record is written, so portal and imported incidents are routed. A service level agreement measures elapsed time against a target, and an update set carries configuration rather than operational data. A flow triggered on creation creates the manager task once per incident.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleConfiguring Applications for Collaborationmedium

Hardware technicians must open incident records on a stripped back form carrying six fields, while service desk agents must keep the current full incident form. Both populations hold the itil role and open the same records from the same lists. Which approach delivers the two layouts with the least duplication of records?

  • ABuild a UI policy on the incident table that hides the surplus fields whenever the logged in user belongs to the hardware technician group.
  • BAsk the hardware technicians to use Personalize Form and drop the fields they do not need from their own incident form.
  • CCreate a second incident table with the six required fields and point the hardware technicians at that table instead.
  • DCreate a new form view holding the six fields and add a view rule that applies it for the hardware technicians. Correct
Form views hold separate layouts for one table, and a view rule decides which view a given user or record type receives. A view is a named layout stored against the table, so the same incident record can render differently without duplicating data. The view rule evaluates when the form opens and selects the view, which is why one record set can serve two populations with different field sets.

Why A is wrong: Tempting because it does produce a shorter form, but hidden fields still occupy the layout and every future field needs adding to the policy, so the maintenance grows with the form.

Why B is wrong: Tempting because personal layout is quick and needs no configuration, but it depends on each technician doing it and is lost for anyone who joins the team afterwards.

Why C is wrong: Tempting because a smaller table would certainly render a smaller form, but it splits the incident data across two tables and breaks reporting, assignment and the shared list the two groups work from.

Why D is correct: A view stores its own form layout for the same table and records, and a view rule selects that view for the matching users, so one set of records serves two layouts.

Free sampleConfiguring Applications for Collaborationmedium

An administrator amends the Assignment group on an open change request and must choose between the Save action and the Update action. Select TWO statements that correctly describe how the two actions differ.

  • ASave writes the amended value to the record and leaves the administrator on the same form, ready to make further edits to it. Correct
  • BUpdate writes the amended value into a fresh copy of the change request, leaving the record that was originally opened unchanged.
  • CSave holds the amended value in the browser until Update is chosen, so that nothing reaches the database before that second step.
  • DUpdate writes the same amended value and then navigates away from the form, usually back to the list or page visited beforehand. Correct
  • ESave writes the amended value and then returns to the list view, while Update keeps the administrator on the change request form.
Save and Update both commit the current record, and they differ only in whether the form stays open or navigation returns to the previous page. Both actions issue an update against the record already open, so the data outcome is identical and neither creates a second record. The difference is purely navigational: Save reloads the same record on the form so editing can continue, while Update returns the user to whatever list or page they came from. Knowing this rules out any option that claims one of them defers the write or inserts a copy.

Why A is correct: Save commits the change and reloads the same record on the form, which is the distinguishing behaviour of that action.

Why B is wrong: Creating a copy is what the insert actions do, so this is a plausible confusion, but Update always writes back to the record already open.

Why C is wrong: Tempting because Save can feel like a draft step, but Save issues a real write, so the change is persisted immediately.

Why D is correct: Update commits the change and returns the user to the previous page, which is the only behavioural difference from Save.

Why E is wrong: This states the correct pair of behaviours with the two actions swapped, which is the most common way candidates lose the point.

Free sampleConfiguring Applications for Collaborationmedium

A table has two separate requirements: one field must arrive prefilled on every new record with no user action at all, and a further set of field values must be available for a user to apply to some new records but not others. Which pairing of platform mechanisms meets both requirements?

  • AA template for the automatic prefill, and a dictionary default value for the values a user chooses to apply.
  • BA UI policy for the automatic prefill, and a dictionary default value for the values a user chooses to apply.
  • CA dictionary default value for the automatic prefill, and a template for the values a user chooses to apply. Correct
  • DA dictionary default value for the automatic prefill, and a UI policy for the values a user chooses to apply.
Separate a field default value, which fills every new record automatically, from a template, which a user applies on demand. A default value is part of the field definition, so the platform seeds it whenever a new record of that table is created and no one has to ask for it. A template is a stored set of field values held separately from the fields themselves and written onto the record only when someone applies it, which is what makes it selective.

Why A is wrong: This is the correct pair of mechanisms in the wrong order; a template needs a deliberate action to apply it, so it cannot supply a value that must appear unprompted.

Why B is wrong: A UI policy can set a field value through its scripting, which makes it look viable, but it governs form behaviour rather than seeded content, and a default value is not something a user opts into.

Why C is correct: A default value defined on the field populates every new record automatically, while a template supplies a named group of values that a user applies only to the records that need them.

Why D is wrong: The first half is right, yet a UI policy runs on its own conditions rather than on request, so it cannot serve as an optional set of values a user picks per record.

Free sampleConfiguring Applications for Collaborationmedium

A team tracks an office move on a freeform Visual Task Board, creating each piece of work as a card directly on the board. The service owner now asks that the same work appear in the change request list and be counted in change reporting alongside everything else the team runs. Which action meets the request?

  • AAdd the change request table as a second data source on the existing freeform board and map the current lanes to Change state
  • BRename each freeform lane to a Change state value so that the board cards are picked up by the change request list and its reports
  • CShare the freeform board with the service owner and grant the owner rights so the cards become visible to change reporting
  • DRaise a change request for each piece of work and build a flexible or guided board on the change request table instead Correct
Recognise that freeform board cards live with the board, so work needing to appear in a table's list and reports must be created as records there. A board built on a table shows cards that are views of existing records, so those records remain available to lists, filters and reporting. A freeform board has no such source and its cards exist as the board's own task records, which is why moving that work into a process means creating records on the process table and then building a flexible or guided board over them.

Why A is wrong: Tempting because a board does associate lanes with a field elsewhere, but a freeform board has no data source to extend and cannot be converted by adding one.

Why B is wrong: Plausible because matching names make the board read like the process, but a lane name is display text and creates no relationship between a card and a record on another table.

Why C is wrong: Attractive because sharing does widen who can open a board, but reporting reads records from tables rather than board cards, and no permission change alters where a card is stored.

Why D is correct: Correct because cards on a freeform board are the board's own task records, so work that must live in the change process has to be created there and then surfaced on a board built from that table.

Free sampleConfiguring Applications for Collaborationmedium

Incidents raised with Impact 1 and Urgency 1 must be assigned to the group Major Incident Team, and a separate task record must be created for the on call manager whenever such an incident is raised. The administrator wants each half of the requirement handled by the mechanism intended for it. Which TWO mechanisms should be used? Select TWO.

  • AA UI policy on the Incident table that sets Assignment group to Major Incident Team once both Impact and Urgency are set to the value 1 on the form.
  • BAn assignment rule on the Incident table carrying a condition on Impact and Urgency that sets Assignment group to Major Incident Team as the record is written. Correct
  • CAn onLoad client script that reads Impact and Urgency, then writes the assignment group and inserts the extra manager task whenever the incident form is opened.
  • DA flow built in Workflow Studio triggered when an incident is created, carrying a condition on Impact and Urgency, that creates the task record for the on call manager. Correct
  • EAn update set holding the group record and the manager task record, committed on the instance so that both records are produced again for every new major incident.
Choose an assignment rule for routing a task and a Workflow Studio flow for creating a related record, rather than form level or migration tooling. Routing and record creation are separate jobs with separate intended mechanisms. An assignment rule evaluates on the server as the incident is written and populates the assignment fields, so it is unaffected by how the record was raised. A flow triggered on creation evaluates the same field values and runs a create record action once per trigger, which gives exactly one manager task. Form level tooling and update sets address neither job.

Why A is wrong: UI policies are the right no-code choice for making fields mandatory, read only or visible, but they act on the form in the browser, so they do not route records raised through an integration.

Why B is correct: Assignment rules exist specifically to populate the assignment fields on task records from conditions, which is the intended mechanism for routing and needs no script to maintain.

Why C is wrong: Client scripting can read those fields, which makes it look workable, but an onLoad script fires every time the form opens and would create duplicate manager tasks on each view.

Why D is correct: A flow is the current no-code mechanism for creating related records in response to a trigger, and its create record action produces the manager task once for each qualifying incident.

Why E is wrong: Update sets are a familiar way to move configuration between instances, but they carry configuration records rather than operational data and they do not run in response to a new incident.

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.