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 16

Question 150

A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed. Which configuration or administrative response BEST addresses the primary issue?

  1. Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record.
  2. Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible.
  3. Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts.
  4. Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms.

Explanation

Correct Answer

A:

Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. The platform coordinates records and workflow actions; a notification, dashboard, or module link is not a substitute for task state and ownership. Verify prerequisites with: Inspect the target task table, assignment fields, state model, user authorization, notifications, and existing fulfillment workflow. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

Incorrect Answers

B:

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: Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

C:

Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts. This approach instead addresses Platform analytics as a reporting capability. Analytics provides views of governed source data, not a replacement for the underlying record lifecycle or ACL model. The targeted response is: Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

D:

Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms. This approach instead addresses Instance lifecycle and environment separation. ServiceNow instances have separate data/configuration state; personal developer or test instances should not be treated as production replicas without controlled clones and access. The targeted response is: Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

Question 151

A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls.
  2. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  3. Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs.
  4. Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration.
  5. Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies.

Explanation

Correct Answers

C:

Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. 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. The appropriate response is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

D:

Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. 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. Verify prerequisites with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. 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:

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 supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

B:

Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. This step may apply to Audit and accountability for privileged instance operations but is not one of the complementary requirements in this case. The intended pair is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

E:

Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. This step may apply to CMDB health completeness correctness and relationship audits but is not one of the complementary requirements in this case. The intended pair is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: A discovery tool changes an asset serial-number format, and the IRE begins creating new records for devices that already exist.

Question 152

A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications.
  2. Review task table, assignment group, assigned user, group membership, reassignment audit, and current state.
  3. Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions.
  4. Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work.
  5. Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.

Explanation

Correct Answers

B:

Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. A task assigned to a group but not an individual is group work, not proof any specific agent owns it. The appropriate response is: Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. Scenario: A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue.

D:

Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. A task assigned to a group but not an individual is group work, not proof any specific agent owns it. Verify prerequisites with: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue.

Incorrect Answers

A:

One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications. This step may apply to Business Rule recursion and idempotent side effects but is not one of the complementary requirements in this case. The intended pair is: Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. Together with: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue.

C:

Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. This step may apply to Task approval and state workflow audit but is not one of the complementary requirements in this case. The intended pair is: Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. Together with: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue.

E:

Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. This step may apply to List versus form anatomy and record identity but is not one of the complementary requirements in this case. The intended pair is: Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. Together with: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: A new incident is assigned to the Network group but no engineer is selected; management claims it is already in a named person's queue.

Question 153

A help desk wants a standard low-priority template for routine device incidents but assumes templates prohibit agents from changing Priority. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result.
  2. The intended users see the approved form field order while role-based access and record data remain intact.
  3. One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue.
  4. A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values.

Explanation

Correct Answer

A:

A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. Scenario: A help desk wants a standard low-priority template for routine device incidents but assumes templates prohibit agents from changing Priority.

Incorrect Answers

B:

The intended users see the approved form field order while role-based access and record data remain intact. This result would support Form Designer and field ordering by view, not the specific outcome required in the case. The relevant acceptance test is: A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result. Scenario: A help desk wants a standard low-priority template for routine device incidents but assumes templates prohibit agents from changing Priority.

C:

One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue. This result would support Event-driven messaging and notification diagnostics, not the specific outcome required in the case. The relevant acceptance test is: A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result. Scenario: A help desk wants a standard low-priority template for routine device incidents but assumes templates prohibit agents from changing Priority.

D:

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: A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result. Scenario: A help desk wants a standard low-priority template for routine device incidents but assumes templates prohibit agents from changing Priority.

Question 154

A service map contains a technical service but no association to the business application it supports. Which configuration or administrative response BEST addresses the primary issue?

  1. Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact.
  2. Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration.
  3. Load external data into an import set staging table and use a reviewed transform map for mapping to a target table, checking row errors rather than inserting directly into arbitrary production tables.
  4. Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb.

Explanation

Correct Answer

A:

Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. CSDM provides consistent service modeling conventions, not a single generic CI class into which all offerings and applications should be placed. Verify prerequisites with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: A service map contains a technical service but no association to the business application it supports.

Incorrect Answers

B:

Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. This approach instead addresses CMDB Identification and Reconciliation Engine source trust. 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. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: A service map contains a technical service but no association to the business application it supports.

C:

Load external data into an import set staging table and use a reviewed transform map for mapping to a target table, checking row errors rather than inserting directly into arbitrary production tables. This approach instead addresses Import set staging and transform-map field mappings. Import set staging and transformation separate source ingestion from target writes; a successful file upload alone is not a completed import. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: A service map contains a technical service but no association to the business application it supports.

D:

Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. This approach instead addresses List filter conditions and breadcrumb logic. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: A service map contains a technical service but no association to the business application it supports.

Question 155

A form collects issue information but no mapping sends those producer variables to the newly created case. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Dragging a data-driven card produces the intended authorized record state/field change, while freeform boards behave according to their configured model.
  2. Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result.
  3. Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions.
  4. Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle.
  5. Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design.

Explanation

Correct Answers

C:

Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. The appropriate response is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

D:

Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. Verify prerequisites with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

Incorrect Answers

A:

Dragging a data-driven card produces the intended authorized record state/field change, while freeform boards behave according to their configured model. This step may apply to Visual Task Board data-driven and freeform handling but is not one of the complementary requirements in this case. The intended pair is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

B:

Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. 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: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

E:

Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. This step may apply to Workflow Studio debugging and Run As privileges but is not one of the complementary requirements in this case. The intended pair is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

Question 156

A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience.
  2. Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions.
  3. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.
  4. Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context.

Explanation

Correct Answer

B:

Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Reusing knowledge is valuable only if ownership, currency and intended audience are maintained; a search hit is not proof of current policy. The appropriate response is: Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

Incorrect Answers

A:

Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. This evidence is relevant to Now Platform shared records and configurable applications, not the most diagnostic first check for this failure. Examine: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

C:

Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. This evidence is relevant to Virtual Agent integrated knowledge and catalog fulfillment, not the most diagnostic first check for this failure. Examine: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

D:

Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. This evidence is relevant to Knowledge search feedback and content improvement, not the most diagnostic first check for this failure. Examine: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

Question 157

A manager wants a change to close automatically when the last approval request was merely delivered to the mailbox. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log.
  2. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.
  3. Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions.
  4. Review task table, assignment group, assigned user, group membership, reassignment audit, and current state.

Explanation

Correct Answer

A:

Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. Task states, approval records and email notifications have distinct meanings; an email sent does not mean approval granted. The appropriate response is: Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. Scenario: A manager wants a change to close automatically when the last approval request was merely delivered to the mailbox.

Incorrect Answers

B:

Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration. This evidence is relevant to Related lists and record relationships, not the most diagnostic first check for this failure. Examine: Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. Scenario: A manager wants a change to close automatically when the last approval request was merely delivered to the mailbox.

C:

Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. This evidence is relevant to User group and role assignment principle of least privilege, not the most diagnostic first check for this failure. Examine: Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. Scenario: A manager wants a change to close automatically when the last approval request was merely delivered to the mailbox.

D:

Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. This evidence is relevant to Task assignment group versus individual responsibility, not the most diagnostic first check for this failure. Examine: Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. Scenario: A manager wants a change to close automatically when the last approval request was merely delivered to the mailbox.

Question 158

A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff. Which configuration or administrative response BEST addresses the primary issue?

  1. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  2. Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification.
  3. Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data.
  4. Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome.

Explanation

Correct Answer

C:

Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. A chat session ending without a supported answer is not a successfully completed service request; escalation must be observable. Verify prerequisites with: Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

Incorrect Answers

A:

Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. This approach instead addresses Per-user list and form personalization. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The targeted response is: Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

B:

Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. This approach instead addresses Virtual Agent integrated knowledge and catalog fulfillment. A Virtual Agent's conversational acknowledgment cannot substitute for a confirmed catalog order or an authorized knowledge article. The targeted response is: Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

D:

Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. This approach instead addresses Virtual Agent topic routing and conversation state. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. The targeted response is: Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

Question 159

An onBefore transform script inadvertently ignores every row with a blank optional phone field. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows.
  2. Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes.
  3. Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.
  4. Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user.

Explanation

Correct Answer

A:

Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. External display strings do not necessarily identify reference records, and scripts can create side effects beyond a simple field map. The appropriate response is: Resolve imported reference values and apply documented transform scripts only when ordinary field mapping is insufficient, with safe handling of absent targets. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

Incorrect Answers

B:

Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. This evidence is relevant to Dictionary attributes and field type integrity, not the most diagnostic first check for this failure. Examine: Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

C:

Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. This evidence is relevant to Import set staging and transform-map field mappings, not the most diagnostic first check for this failure. Examine: Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

D:

Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. This evidence is relevant to Per-user list and form personalization, not the most diagnostic first check for this failure. Examine: Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

Question 160

A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references.
  2. Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records.
  3. The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations.
  4. Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.
  5. Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects.

Explanation

Correct Answers

A:

Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. Verify prerequisites with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.

D:

Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. The appropriate response is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Scenario: A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.

Incorrect Answers

B:

Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. This step may apply to Related lists and record relationships but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.

C:

The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations. This step may apply to Application installation and plugin activation preflight but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.

E:

Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. This step may apply to Visual Task Board data-driven and freeform handling but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.

ServiceNow Certified System Administrator (CSA) Practice Tests