Free CSA sample questions with answers
Try these 10 free CSA practice questions covering forms, security, the Service Catalog, flows and data imports. Choose your answer, then check it to see an explanation for every option.
These questions are original and written from the official exam blueprint. They are not real exam questions. The full course has 304 questions in 5 timed exams.
New to this exam? Read the ServiceNow CSA Study Guide: Exam Blueprint, Key Topics and a 6-Week Plan first.
- Question 1 of 10Instance ConfigurationMultiple select
Show answer & explanations
Correct answers: B, D
- A. A new user recordUser records are data and are not captured by default.
- B. A change to a form layoutCorrect. Form layout changes are customizations and are captured.
- C. A new incident recordIncidents are data, not configuration, and are not captured.
- D. A new Business RuleCorrect. Business Rules are configuration records and are tracked in the current update set.
Explanation: Update sets capture customizations (configuration records such as scripts, forms, lists and dictionary entries). Data records like tasks and users must be moved another way, for example with XML export or import sets.
- Question 2 of 10Database Management and Platform SecuritySingle answer
Show answer & explanations
Correct answer: D
- A. Field-level ACLs are only evaluated for adminsField ACLs apply to all users; admins often pass them because of the admin role.
- B. Passing the table-level ACL automatically grants access to every fieldField ACLs are evaluated in addition to table ACLs.
- C. ACLs only control list views, not formsACLs control access in forms, lists, APIs and reports.
- D. The user must pass both the table-level ACL and the field-level ACL to access a fieldCorrect. Passing the table ACL grants the row; each field is then checked against its own field ACL.
Explanation: Access is granted only when the user satisfies the role, condition and script of a matching ACL at both the table (row) and field level.
- Question 3 of 10Database Management and Platform SecuritySingle answer
Show answer & explanations
Correct answer: D
- A. A copy of all fields from the referenced recordReference fields do not copy data.
- B. The display value of the referenced recordDisplay values are shown in the UI, but not stored.
- C. The table name and record numberOnly the sys_id is stored; the table is defined on the dictionary entry.
- D. The sys_id of the referenced recordCorrect. The display value is looked up from the referenced record; the stored value is its sys_id.
Explanation: Because references point to sys_ids, you can dot-walk to fields on the referenced record, and renaming a record does not break the relationship.
- Question 4 of 10Database Management and Platform SecuritySingle answer
Show answer & explanations
Correct answer: D
- A. Changing the default value on the Task dictionary entryThat would affect every table extending Task.
- B. Creating a new Priority field on IncidentThis would duplicate data and break processes using the inherited field.
- C. A client script that sets the value onLoadIt would only run in forms and is not the configuration-based solution.
- D. A dictionary overrideCorrect. Dictionary overrides let a child table change inherited field properties such as default value, mandatory or read-only.
Explanation: Dictionary overrides are the supported way to vary inherited field behaviour per child table without affecting the parent or sibling tables.
- Question 5 of 10Self-Service and AutomationSingle answer
Show answer & explanations
Correct answer: B
- A. Variable setVariable sets are reusable groups of variables.
- B. Record producerCorrect. Record producers map catalog variables to fields on a target table.
- C. Order guideOrder guides bundle multiple catalog items into one request.
- D. Catalog client scriptClient scripts add form behaviour; they are not an item type.
Explanation: Record producers give end users a friendly catalog experience while creating task records such as incidents, HR cases or changes.
- Question 6 of 10Configuring Applications for CollaborationMultiple select
Show answer & explanations
Correct answers: A, C, D
- A. Who will receiveCorrect. Defines users, groups or fields that contain recipients.
- B. How to escalateEscalation is handled by SLAs or flows, not notifications.
- C. When to sendCorrect. Defines the table, trigger (record inserted/updated or event) and conditions.
- D. What it will containCorrect. Defines subject, message body or an email template.
- E. Where to storeNot a notification section; sent emails are logged automatically.
Explanation: Every notification answers three questions (when, who and what). Using events as triggers and templates for content keeps notifications reusable.
- Question 7 of 10Data Migration and IntegrationSingle answer
Show answer & explanations
Correct answer: C
- A. The order of rows in the source fileRow order does not control insert versus update.
- B. The import set table nameThe staging table name has no influence on matching.
- C. A field marked as coalesce in the transform mapCorrect. Coalesce fields are used to match existing target records; if a match is found, the record is updated.
- D. The data source type (Excel or CSV)The file format does not affect matching.
Explanation: Without a coalesce field every row is inserted as a new record. Choose a unique, stable field (e.g., employee number or email) to coalesce on.
- Question 8 of 10Instance ConfigurationSingle answer
Show answer & explanations
Correct answer: D
- A. A data policyData policies enforce mandatory/read-only at the data level but cannot hide fields.
- B. An ACLACLs control security, not conditional visibility for usability.
- C. A before Business RuleBusiness rules run on the server and do not control form visibility.
- D. A UI policyCorrect. UI policies can show/hide, make mandatory or read-only fields based on conditions without scripting.
Explanation: Prefer UI policies over client scripts for simple form behaviour. They are declarative, easier to maintain and upgrade-safe.
- Question 9 of 10Self-Service and AutomationMultiple select
Show answer & explanations
Correct answers: A, C, D
- A. Date (scheduled)Correct. Fires on a daily, weekly, monthly or repeating schedule.
- B. Client clickNot a Flow Designer trigger type.
- C. ApplicationCorrect. Fires from application events such as Service Catalog requests or inbound email.
- D. RecordCorrect. Fires when a record is created or updated.
- E. Form loadFlows run on the server and are not triggered by form loads.
Explanation: Flow Designer lets admins automate processes with low code. Choosing the right trigger type is the first design decision for every flow.
- Question 10 of 10Platform Overview and NavigationSingle answer
Show answer & explanations
Correct answer: A
- A. Impersonate the userCorrect. Impersonation shows the UI with the user's roles and permissions.
- B. Export the user's roles to ExcelUseful for analysis, but it does not show the actual experience.
- C. Clear the instance cacheCaching rarely causes role-based visibility issues.
- D. Grant the admin role to the user temporarilyThis changes the user's access and would hide the original problem.
Explanation: Impersonation is the standard way to troubleshoot roles, ACLs and module visibility. Actions taken while impersonating are recorded as the impersonated user, so use a sub-production instance where possible.
Your result
0 / 10