CSA - Configuring Applications for Collaboration (20% of the exam) - Section 3

Form Configuration

Using Form Design and Form Layout to add, remove and arrange fields and sections, creating views, configuring related lists, the difference between configuring a form for everyone and personalising it for one user, and how form views map to roles and record types.

Form DesignerForm views

Practice question for this objective

Free sampleConfiguring Applications for Collaborationmedium

An administrator arranges the fields on a long form into labelled groups so that related fields sit together, and each group renders as its own tab when the form is displayed in a tabbed layout. Which element is being configured?

AForm sections, which divide the fields of one record into labelled groups that render as tabs in a tabbed layout. Correct
BRelated lists, which display records held on other tables that reference the record currently open on the form.
CForm views, which decide the whole layout a given audience is shown rather than how fields are grouped inside that layout.
DUI actions, which place buttons and links on the form and run their configured logic against the record when selected.

Understand that form sections group the fields of a single record and that a tabbed form layout renders each section as one tab. A section belongs to a form view and holds an ordered set of fields from the record being displayed. Whether those groups appear stacked with headings or as tabs is a presentation preference applied to the same underlying sections, so the grouping is configured once at section level.

Why A is correct: Correct because a section is the grouping unit within a form layout, and the tabbed presentation simply renders each configured section as a separate tab.

Why B is wrong: Tempting because related lists also appear as tabs in some layouts, but they carry records from other tables rather than fields of the record on screen.

Why C is wrong: Tempting because views and sections are configured from the same form designer, but a view is the container and the sections sit within it.

Why D is wrong: Tempting because UI actions are also positioned during form configuration, but they are controls that execute logic and never group fields.

See more CSA practice questions, answers explained.

Exam traps in Configuring Applications for Collaboration

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.

Ask each agent to open Personalize Form on the incident record and clear the Impact field for themselves.
Why it is wrong: Tempting because it does produce the wanted result on each screen, but it repeats a personal change for every user and leaves new starters seeing the field, so it is maintenance rather than configuration.
Add a read only string field to the change request table and set the instruction as its default value on the form.
Why it is wrong: Tempting because the text would render where it is wanted, but it adds a column to every change record and stores the instruction as data on each one, which is not what the requirement asks for.
Add the department field to the incident form through the form layout, then filter the incident list on that newly added field with a value of Finance.
Why it is wrong: Tempting because form layout does surface related information, but placing a field on a form does not create a column on the incident record for the filter to evaluate.

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