Text preview & study summary

ServiceNow CSA - Certified System Administrator - User Interface Navigation Administration Configuration

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

A developer needs to debug a server-side script in ServiceNow. Which tool allows them to run GlideRecord scripts interactively against live data without creating a formal script record?

Answer choices

  • A. JavaScript Debugger in the browser developer tools

  • B. Script Editor with syntax highlighting

  • C. Scripts - Background (System Definition > Scripts - Background) (Correct)

  • D. Business Rule Preview mode

Explanation

Scripts - Background (navigate to System Definition > Scripts - Background, or type `sys.scripts.do` in the navigator) is ServiceNow's interactive server-side scripting console. Developers can write and execute arbitrary server-side JavaScript including GlideRecord queries, GlideSystem calls, and other server APIs against live instance data immediately. The output is displayed in the console. This is the primary debugging tool for server-side logic. The browser's JavaScript Debugger (option A) only handles client-side scripts. Business rules don't have a "preview" mode for execution.

Question 2

A user complains that when they open an incident assigned to them, they can see the record but cannot update any fields. The user has the `itil` role. What is the MOST likely cause?

Answer choices

  • A. The incident is in "Resolved" or "Closed" state and is read-only by platform default

  • B. An ACL write rule is preventing the user from updating the record (Correct)

  • C. The user's browser cache is corrupted

  • D. The incident record belongs to a different domain in a multi-domain instance

Explanation

While options A and D are plausible in specific environments, the MOST likely cause in a standard scenario where a user with the `itil` role can VIEW but not EDIT is an ACL write restriction. ACLs can be configured to allow read but deny write based on conditions (e.g., only the assigned user can edit, or only certain states allow editing). The administrator should inspect the ACL rules for the Incident table's write permission. Option A is possible if state-based read-only is configured, but that would typically show a message. Domain separation (option D) would more likely prevent viewing entirely.

Question 3

A company has acquired a new subsidiary and needs to keep their ServiceNow data completely separate from the parent company's data while operating in the same instance. Which ServiceNow feature addresses this requirement?

Answer choices

  • A. Scoped Applications to isolate application logic

  • B. Domain Separation to partition data, processes, and configurations by organizational entity (Correct)

  • C. Update Sets to separate configuration changes

  • D. Role-based access control with custom roles for each entity

Explanation

Domain Separation is ServiceNow's enterprise feature for multi-tenant data and configuration isolation within a single instance. Each domain (parent company, subsidiary) maintains its own set of records, configurations, and processes. Users in one domain cannot see another domain's data unless explicitly granted cross-domain access. This is the correct architectural solution for acquired subsidiary isolation. Scoped Applications (option A) isolate application code and configuration but don't partition data. RBAC (option D) can restrict access but doesn't provide true data partitioning. Domain Separation is specifically designed for this organizational segmentation requirement.

Question 4

A manager wants a report that shows the number of open incidents grouped by priority and assignment group, refreshed every morning at 8 AM and emailed to her team. Which combination of ServiceNow features accomplishes this?

Answer choices

  • A. A performance analytics widget on a dashboard, manually shared each day

  • B. A report with appropriate grouping conditions, saved and added to a Scheduled Report that sends via email (Correct)

  • C. A list view exported to Excel manually each morning

  • D. A gauge widget that displays live counts without email capability

Explanation

ServiceNow Reports can be created with group-by conditions (Priority, Assignment Group) and filtered for open state. Once saved, reports can be added to Scheduled Reports (under Reports > Scheduled) which run on a defined schedule (daily at 8 AM) and automatically email the output to specified recipients. Performance Analytics widgets require a separate PA license and are for trend analysis over time. Manual exports do not meet the automation requirement.

Question 5

An administrator wants to prevent users from submitting an Incident form if the "Short Description" field is empty. What is the CORRECT way to enforce this?

Answer choices

  • A. Create a UI Policy that makes the field mandatory (required)

  • B. Create a Client Script of type "onSubmit" that checks the field value and returns false if empty

  • C. Add a Data Policy that marks the Short Description field as mandatory

  • D. Both A and C are correct but C is preferred for API/import enforcement (Correct)

Explanation

UI Policies enforce mandatory fields in the browser UI—they prevent form submission visually. However, UI Policies only affect the Service Portal or desktop UI and don't apply to API calls or data imports. Data Policies apply across all ingestion paths including REST API, imports, and direct database operations. For comprehensive enforcement, Data Policies are preferred. In practice, many organizations use both: UI Policy for user-friendly real-time feedback and Data Policy for platform-wide enforcement. The question specifically says "prevent users from submitting"—both approaches work, but Data Policy is architecturally superior.