cert
cert-1
cert-2

Pass ServiceNow CSA Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
CSA Exam - Verified By Experts
CSA Premium Bundle
$29.98

CSA Premium Bundle

$79.99
$109.97
  • Premium File 419 Questions & Answers. Last update: Nov 21, 2026
  • Training Course 104 Video Lectures
  • Study Guide 567 Pages
 
$109.97
$79.99
accept 55 downloads in last 7 days
block-screenshots
Purchase ServiceNow CSA Exam Training Products Individually
ServiceNow CSA Premium File
Premium File 419 Q&A
$76.99$69.99
ServiceNow CSA Video Training Course
Training Course 104 Lectures
$21.99 $19.99
ServiceNow CSA PDF Study Guide
Study Guide 567 Pages
$21.99 $19.99
ServiceNow CSA Practice Test 85

Question 840

An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role. Which configuration or administrative response BEST addresses the primary issue?

  1. Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible.
  2. Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations.
  3. Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout.
  4. Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.

Explanation

Correct Answer

B:

Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. Verify prerequisites with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Incorrect Answers

A:

Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. This approach instead addresses User group and role assignment principle of least privilege. Roles control capabilities while groups often organize work and confer roles; assignment to a task group does not inherently grant all administrator privileges. The targeted response is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

C:

Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. This approach instead addresses Unified navigation between workspaces and platform views. Workspace experience and traditional platform form views can differ in component layout and configuration, even when they operate on shared records. The targeted response is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

D:

Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. This approach instead addresses Scheduled data imports and operational cleanup. Scheduled imports require data quality, monitoring and cleanup as well as a timer; large or overlapping batches can harm platform performance. The targeted response is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Question 841

A team uses the same tag name to group tasks and assumes it changed every task's assigned user. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes.
  2. Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy.
  3. Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership.
  4. Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history.

Explanation

Correct Answer

B:

Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. Tags organize records and filters select records; neither overrides read permissions nor creates task assignment automatically. The appropriate response is: Use tags and saved filters for organizing or retrieving records while setting ownership and sharing appropriately; do not treat a label as a role or ACL. Scenario: A team uses the same tag name to group tasks and assumes it changed every task's assigned user.

Incorrect Answers

A:

Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. This evidence is relevant to Form Designer and field ordering by view, not the most diagnostic first check for this failure. Examine: Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. Scenario: A team uses the same tag name to group tasks and assumes it changed every task's assigned user.

C:

Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. This evidence is relevant to List filter conditions and breadcrumb logic, not the most diagnostic first check for this failure. Examine: Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. Scenario: A team uses the same tag name to group tasks and assumes it changed every task's assigned user.

D:

Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. This evidence is relevant to Next Experience application navigation and favorites, not the most diagnostic first check for this failure. Examine: Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. Scenario: A team uses the same tag name to group tasks and assumes it changed every task's assigned user.

Question 842

A self-service chat selects an ineligible catalog item and silently drops the request without explanation. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification.
  2. Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls.
  3. Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record.
  4. Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome.
  5. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.

Explanation

Correct Answers

A:

Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. A Virtual Agent's conversational acknowledgment cannot substitute for a confirmed catalog order or an authorized knowledge article. Verify prerequisites with: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

E:

Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. A Virtual Agent's conversational acknowledgment cannot substitute for a confirmed catalog order or an authorized knowledge article. The appropriate response is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

Incorrect Answers

B:

Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. This step may apply to Form sections and related layout configuration but is not one of the complementary requirements in this case. The intended pair is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Together with: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

C:

Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. This step may apply to Virtual Agent human handoff and fallback but is not one of the complementary requirements in this case. The intended pair is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Together with: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

D:

Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. This step may apply to Virtual Agent topic routing and conversation state but is not one of the complementary requirements in this case. The intended pair is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Together with: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

Question 843

A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The authorized operator reaches the same intended record in the correct working interface with the expected controls and permissions.
  2. A properly assigned task has an auditable state and owner, and the workflow records its changes rather than relying on emails as the authoritative queue.
  3. The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response.
  4. The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see.

Explanation

Correct Answer

D:

The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. An All menu module is a navigation target, while Favorites is a personal shortcut; absence of a module may instead reflect roles or installed application state. Scenario: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

Incorrect Answers

A:

The authorized operator reaches the same intended record in the correct working interface with the expected controls and permissions. This result would support Unified navigation between workspaces and platform views, not the specific outcome required in the case. The relevant acceptance test is: The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. Scenario: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

B:

A properly assigned task has an auditable state and owner, and the workflow records its changes rather than relying on emails as the authoritative queue. This result would support Platform task and service management capabilities, not the specific outcome required in the case. The relevant acceptance test is: The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. Scenario: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

C:

The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. This result would support Virtual Agent topic routing and conversation state, not the specific outcome required in the case. The relevant acceptance test is: The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. Scenario: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

Question 844

An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  2. Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs.
  3. Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form.
  4. Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations.
  5. Search results lead to the current approved article, and the superseded instructions no longer mislead requesters.

Explanation

Correct Answers

B:

Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. The appropriate response is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

D:

Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. Verify prerequisites with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Incorrect Answers

A:

Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. This step may apply to Scoped application permissions and cross-scope access but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

C:

Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. This step may apply to Table-level versus field-level access controls but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

E:

Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. This step may apply to Knowledge article review, validity and version lifecycle but is not one of the complementary requirements in this case. The intended pair is: Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. Together with: Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Question 845

A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history.
  2. Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database.
  3. Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout.
  4. Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data.
  5. Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience.

Explanation

Correct Answers

B:

Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database. ServiceNow is a multi-tenant cloud platform with configurable applications built around records and tables; navigation modules expose features but do not create isolated physical databases. Verify prerequisites with: Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. Scenario: A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications.

E:

Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. ServiceNow is a multi-tenant cloud platform with configurable applications built around records and tables; navigation modules expose features but do not create isolated physical databases. The appropriate response is: Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database. Scenario: A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications.

Incorrect Answers

A:

Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. This step may apply to Next Experience application navigation and favorites but is not one of the complementary requirements in this case. The intended pair is: Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database. Together with: Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. Scenario: A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications.

C:

Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. This step may apply to Unified navigation between workspaces and platform views but is not one of the complementary requirements in this case. The intended pair is: Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database. Together with: Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. Scenario: A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications.

D:

Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data. This step may apply to Import set staging and transform-map field mappings but is not one of the complementary requirements in this case. The intended pair is: Explain a ServiceNow application as a group of related modules and records built on shared tables, using configuration to serve a business workflow without assuming each app is a separate physical database. Together with: Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. Scenario: A new administrator calls Incident a separate database and proposes manually copying user records between the Incident and Change applications.

Question 846

A user sees a request number and assumes every line item in a multi-item order has completed fulfillment. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions.
  2. The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.
  3. A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values.
  4. Matching rows update the intended existing records and genuinely new rows insert without unintended duplicates or overwrites.

Explanation

Correct Answer

A:

The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions. REQ, RITM and catalog task are distinct records with different scopes; notifying a manager does not imply a requested item was approved. Scenario: A user sees a request number and assumes every line item in a multi-item order has completed fulfillment.

Incorrect Answers

B:

The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step. This result would support Workflow Studio debugging and Run As privileges, not the specific outcome required in the case. The relevant acceptance test is: The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions. Scenario: A user sees a request number and assumes every line item in a multi-item order has completed fulfillment.

C:

A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values. This result would support Service Catalog item variables and validation, not the specific outcome required in the case. The relevant acceptance test is: The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions. Scenario: A user sees a request number and assumes every line item in a multi-item order has completed fulfillment.

D:

Matching rows update the intended existing records and genuinely new rows insert without unintended duplicates or overwrites. This result would support Coalesce keys and update versus insert control, not the specific outcome required in the case. The relevant acceptance test is: The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions. Scenario: A user sees a request number and assumes every line item in a multi-item order has completed fulfillment.

Question 847

A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Authorized users read or write only permitted table rows and fields, and unauthorized API or form access is denied.
  2. The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated.
  3. Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process.
  4. Critical settings and access grants have attributable approved changes and stale privileges are removed after review.

Explanation

Correct Answer

B:

The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Identification and reconciliation distinguish an existing CI from a new one and govern conflicting data sources; a generic coalesce map alone may be insufficient for CMDB integrity. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

Incorrect Answers

A:

Authorized users read or write only permitted table rows and fields, and unauthorized API or form access is denied. This result would support Table-level versus field-level access controls, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

C:

Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. This result would support Knowledge search feedback and content improvement, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

D:

Critical settings and access grants have attributable approved changes and stale privileges are removed after review. This result would support Audit and accountability for privileged instance operations, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

Question 848

A technician applies a form template intended for change requests to an incident and finds unrelated fields not available. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs.
  2. Review task table, assignment group, assigned user, group membership, reassignment audit, and current state.
  3. The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated.
  4. Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes.
  5. Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule.

Explanation

Correct Answers

D:

Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. The appropriate response is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Scenario: A technician applies a form template intended for change requests to an incident and finds unrelated fields not available.

E:

Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. Verify prerequisites with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A technician applies a form template intended for change requests to an incident and finds unrelated fields not available.

Incorrect Answers

A:

Investigate failed or duplicated event-driven notifications by correlating the generated event with notification conditions and outbound delivery logs. This step may apply to Event-driven messaging and notification diagnostics but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A technician applies a form template intended for change requests to an incident and finds unrelated fields not available.

B:

Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. This step may apply to Task assignment group versus individual responsibility but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A technician applies a form template intended for change requests to an incident and finds unrelated fields not available.

C:

The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. This step may apply to CMDB Identification and Reconciliation Engine source trust but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A technician applies a form template intended for change requests to an incident and finds unrelated fields not available.

Question 849

A user may read Incident records but must not read a restricted salary estimate custom field. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form.
  2. Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context.
  3. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  4. The form shows context-appropriate actions and editable fields, while invalid or unauthorized data modifications remain blocked server-side.
  5. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.

Explanation

Correct Answers

A:

Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. Verify prerequisites with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A user may read Incident records but must not read a restricted salary estimate custom field.

B:

Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. The appropriate response is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Scenario: A user may read Incident records but must not read a restricted salary estimate custom field.

Incorrect Answers

C:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This step may apply to Table extension and inherited task fields but is not one of the complementary requirements in this case. The intended pair is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A user may read Incident records but must not read a restricted salary estimate custom field.

D:

The form shows context-appropriate actions and editable fields, while invalid or unauthorized data modifications remain blocked server-side. This step may apply to Advanced form configuration and conditional display but is not one of the complementary requirements in this case. The intended pair is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A user may read Incident records but must not read a restricted salary estimate custom field.

E:

Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. This step may apply to Security Center evidence and posture exception control but is not one of the complementary requirements in this case. The intended pair is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A user may read Incident records but must not read a restricted salary estimate custom field.

Question 850

A form shows a friendly label for a choice field but an import sends an unknown underlying choice value. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change.
  2. The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results.
  3. When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values.
  4. Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data.

Explanation

Correct Answer

A:

The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

Incorrect Answers

B:

The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results. This result would support Reference fields and display values in the data dictionary, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

C:

When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This result would support UI Policy actions for conditional field behavior, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

D:

Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data. This result would support Import set staging and transform-map field mappings, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

ServiceNow Certified System Administrator (CSA) Practice Tests