Question Q-8754 A company requires that every Incident must have a CI…
2 comments · last active May 30, 2026
ServiceNow CSA - Certified System Administrator - User Interface Navigation Administration Configuration
By Marcus Chen · Updated May 25, 2026
| Questions | 25 |
| Passing Score | 75% |
| Format | 100% Multiple Choice |
| Sessions Logged | 581 |
| Your progress | Log in / Register to track times taken, best score, questions mastered, and coverage on this quiz. |
| Rating |
Topics covered
Uncategorized25 questions
Discussion
Log in to post a comment, reply, or expand a question.
Upgrade 'skipped' = customer changed same OOB record baseline also changed. Review Upgrade History → merge or revert — nothing is deleted.
New admins panic on skip count — it's a reconciliation queue, not data loss.
We document every skip in CAB notes before prod upgrade weekend.
Read-only on incident = ACL with Read on table tied to custom role. itil role is full CRUD on ITSM — wrong for view-only.
+2 votesDisplay business rule hides UI; ACL blocks data at platform. Security question always picks ACL.
Group default list layout: create named view via Configure > List Layout as admin, set as default through view selector — not personal list personalization.
Impersonation is great for verifying what each role actually sees after you set the view.
Salary on HR case — field-level ACL on read for hr_manager. UI Policy hides visually but data still hits browser/API without ACL.
Never delete dictionary fields in prod to 'hide' sensitive data. ACL is the control.
Update Sets capture CONFIG changes dev→test→prod — not transactional data. XML export/import is the promotion vehicle.
Batch field update across records is NOT what Update Set means — common beginner trap.
Short description mandatory: UI Policy works in UI only. Data Policy enforces on REST/import too — exam picks D (both, C preferred for API).
+2 votesonSubmit client script can block submit but won't stop integration inserts — know the layers.
Catalog visibility by department = User Criteria on Available For field. Purpose-built for sc_cat_item audience, cleaner than ACL hacks.
Separate catalogs per dept is operational nightmare at 15 items — criteria scales better.
itil user can view but not edit — check write ACLs with conditions (assigned to, state, group). Resolved/closed can be read-only too but ACL is 'most likely' per rationale.
Domain separation usually blocks view entirely, not edit-only weirdness.
PIR after major incident → Problem Management for structured RCA, not just resolution notes field.
KB article documents solution; Problem drives investigation workflow and known error linkage.
Nightly HR CSV from SFTP = Import Set + Transform Map + Scheduled Import. REST endpoint alone doesn't pull the file.
IntegrationHub SFTP spoke is valid in real life but CSA baseline answer is the three-piece import stack.
Acquired subsidiary data isolation = Domain Separation. Scoped apps isolate code; RBAC alone doesn't partition tenant data.
Cross-domain access is grantable but default is hard separation per org entity.
Question catalog for this preview
Catalog listing of the 5 preview questions for this quiz.
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?
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?
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?
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?
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?
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.
CI required before In Progress = before business rule, setAbortAction(true) if cmdb_ci empty. Works for UI and API.
UI Policy on state change doesn't stop REST updates. SLA pause isn't state enforcement.