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 18

Question 170

An analyst maps an external office name into the sys_id of a reference field and creates invalid references. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. 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.
  2. Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.
  3. Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.
  4. Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs.
  5. A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.

Explanation

Correct Answers

A:

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. Import set staging and transformation separate source ingestion from target writes; a successful file upload alone is not a completed import. Verify prerequisites with: Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. Scenario: An analyst maps an external office name into the sys_id of a reference field and creates invalid references.

B:

Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. Import set staging and transformation separate source ingestion from target writes; a successful file upload alone is not a completed import. The appropriate response is: 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. Scenario: An analyst maps an external office name into the sys_id of a reference field and creates invalid references.

Incorrect Answers

C:

Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. This step may apply to Scheduled data imports and operational cleanup but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. Scenario: An analyst maps an external office name into the sys_id of a reference field and creates invalid references.

D:

Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. This step may apply to Elevated security administration and role boundaries but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. Scenario: An analyst maps an external office name into the sys_id of a reference field and creates invalid references.

E:

A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data. This step may apply to Platform analytics as a reporting capability but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. Scenario: An analyst maps an external office name into the sys_id of a reference field and creates invalid references.

Question 171

One analyst wants Caller and Priority moved left in the Incident list without forcing the arrangement on the entire support team. Which configuration or administrative response BEST addresses the primary issue?

  1. Use order guides and appropriately related catalog items when one guided request should include several coordinated deliverables, preserving distinct fulfillment ownership.
  2. Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience.
  3. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  4. Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance.

Explanation

Correct Answer

C:

Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. Verify prerequisites with: Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Scenario: One analyst wants Caller and Priority moved left in the Incident list without forcing the arrangement on the entire support team.

Incorrect Answers

A:

Use order guides and appropriately related catalog items when one guided request should include several coordinated deliverables, preserving distinct fulfillment ownership. This approach instead addresses Service Catalog order guide and request structure. A request can contain multiple requested items; the order-guide experience should not collapse independent approvals or ownership into an untracked generic task. The targeted response is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Scenario: One analyst wants Caller and Priority moved left in the Incident list without forcing the arrangement on the entire support team.

B:

Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. This approach instead addresses Core platform lists versus forms and workspaces. A list aggregates records, a form edits a selected record, and a workspace can wrap multiple components; these are interfaces over records, not independent data copies. The targeted response is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Scenario: One analyst wants Caller and Priority moved left in the Incident list without forcing the arrangement on the entire support team.

D:

Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance. This approach instead addresses Application installation and plugin activation preflight. Activating a plugin may introduce tables, roles and configuration; it is not equivalent to adding a harmless navigation favorite. The targeted response is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Scenario: One analyst wants Caller and Priority moved left in the Incident list without forcing the arrangement on the entire support team.

Question 172

A user asks the chatbot to order a monitor; the bot says done despite no RITM being created. Which configuration or administrative response BEST addresses the primary issue?

  1. Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome.
  2. Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience.
  3. Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification.
  4. Use order guides and appropriately related catalog items when one guided request should include several coordinated deliverables, preserving distinct fulfillment ownership.

Explanation

Correct Answer

C:

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 user asks the chatbot to order a monitor; the bot says done despite no RITM being created.

Incorrect Answers

A:

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: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Scenario: A user asks the chatbot to order a monitor; the bot says done despite no RITM being created.

B:

Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. This approach instead addresses Core platform lists versus forms and workspaces. A list aggregates records, a form edits a selected record, and a workspace can wrap multiple components; these are interfaces over records, not independent data copies. The targeted response is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Scenario: A user asks the chatbot to order a monitor; the bot says done despite no RITM being created.

D:

Use order guides and appropriately related catalog items when one guided request should include several coordinated deliverables, preserving distinct fulfillment ownership. This approach instead addresses Service Catalog order guide and request structure. A request can contain multiple requested items; the order-guide experience should not collapse independent approvals or ownership into an untracked generic task. The targeted response is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Scenario: A user asks the chatbot to order a monitor; the bot says done despite no RITM being created.

Question 173

A service manager embeds a case report on a dashboard without checking whether viewers have permission to read its source table. Which configuration or administrative response BEST addresses the primary issue?

  1. 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.
  2. Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference.
  3. Select the supported form or workspace configuration tool for the desired interface and preview the outcome in a scoped test context before promoting it.
  4. 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.

Explanation

Correct Answer

A:

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. Analytics provides views of governed source data, not a replacement for the underlying record lifecycle or ACL model. Verify prerequisites with: Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Scenario: A service manager embeds a case report on a dashboard without checking whether viewers have permission to read its source table.

Incorrect Answers

B:

Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference. This approach instead addresses Next Experience application navigation and favorites. 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. The targeted response is: 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. Scenario: A service manager embeds a case report on a dashboard without checking whether viewers have permission to read its source table.

C:

Select the supported form or workspace configuration tool for the desired interface and preview the outcome in a scoped test context before promoting it. This approach instead addresses Configurable form and workspace layout changes. Traditional form layout tools and modern workspace configuration can target different surfaces; presentation changes do not replace table security. The targeted response is: 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. Scenario: A service manager embeds a case report on a dashboard without checking whether viewers have permission to read its source table.

D:

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. This approach instead addresses Now Platform shared records and configurable applications. 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 targeted response is: 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. Scenario: A service manager embeds a case report on a dashboard without checking whether viewers have permission to read its source table.

Question 174

An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching. Which configuration or administrative response BEST addresses the primary issue?

  1. Separate configuration capture from application data migration, review update set collisions, and keep manual data-loading tasks explicit rather than assuming a commit reproduces every record.
  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. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.
  4. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.

Explanation

Correct Answer

C:

Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. Verify prerequisites with: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.

Incorrect Answers

A:

Separate configuration capture from application data migration, review update set collisions, and keep manual data-loading tasks explicit rather than assuming a commit reproduces every record. This approach instead addresses Update set exclusions and collision resolution. System update sets are not a general backup or complete data-migration mechanism; preview and conflict management protect target instances. The targeted response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.

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: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.

D:

Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. This approach instead addresses Audit and accountability for privileged instance operations. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. The targeted response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.

Question 175

A tab is hidden through a form change but the required field in that tab still blocks submission. 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. Review indicator/report source, filter conditions, dashboard permissions, viewer roles, date range, and refresh behavior.
  3. Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs.
  4. Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.

Explanation

Correct Answer

D:

Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Changing a form section only changes presentation; a dictionary requirement or ACL still applies after fields are rearranged. The appropriate response is: Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Scenario: A tab is hidden through a form change but the required field in that tab still blocks submission.

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: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A tab is hidden through a form change but the required field in that tab still blocks submission.

B:

Review indicator/report source, filter conditions, dashboard permissions, viewer roles, date range, and refresh behavior. This evidence is relevant to Dashboards and Platform Analytics audience permissions, not the most diagnostic first check for this failure. Examine: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A tab is hidden through a form change but the required field in that tab still blocks submission.

C:

Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. This evidence is relevant to CMDB Identification and Reconciliation Engine source trust, not the most diagnostic first check for this failure. Examine: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A tab is hidden through a form change but the required field in that tab still blocks submission.

Question 176

An incident form must show its associated tasks but a related list is empty because the child reference field points to another incident. Which configuration or administrative response BEST addresses the primary issue?

  1. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.
  2. Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout.
  3. 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.
  4. 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.

Explanation

Correct Answer

C:

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. A related list is a query-backed view of associated records; it does not inherently store copies of all child rows on the parent. Verify prerequisites with: Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration. Scenario: An incident form must show its associated tasks but a related list is empty because the child reference field points to another incident.

Incorrect Answers

A:

Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. This approach instead addresses Security Center evidence and posture exception control. Accepting a known exception is a governance decision, not evidence the security configuration meets the baseline. The targeted response is: 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. Scenario: An incident form must show its associated tasks but a related list is empty because the child reference field points to another incident.

B:

Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout. This approach instead addresses Dashboards and Platform Analytics audience permissions. Sharing a dashboard is not a substitute for table ACLs; chart accuracy depends on data definitions and refresh timing. The targeted response is: 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. Scenario: An incident form must show its associated tasks but a related list is empty because the child reference field points to another incident.

D:

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. This approach instead addresses List versus form anatomy and record identity. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. The targeted response is: 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. Scenario: An incident form must show its associated tasks but a related list is empty because the child reference field points to another incident.

Question 177

A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. 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.
  2. A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.
  3. The authorized operator reaches the same intended record in the correct working interface with the expected controls and permissions.
  4. UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors.

Explanation

Correct Answer

A:

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. The platform coordinates records and workflow actions; a notification, dashboard, or module link is not a substitute for task state and ownership. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

Incorrect Answers

B:

A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data. This result would support Platform analytics as a reporting capability, not the specific outcome required in the case. The relevant acceptance test is: 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. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

C:

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: 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. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

D:

UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. This result would support Client script versus Business Rule and API persistence, not the specific outcome required in the case. The relevant acceptance test is: 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. Scenario: A manager needs to distinguish a real recorded approval decision from a notification telling someone an approval might be needed.

Question 178

A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.
  2. Check instance URL and identity, release family, data sensitivity, clone schedule, environment role, and promotion approval.
  3. Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization.
  4. Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history.

Explanation

Correct Answer

C:

Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Analytics provides views of governed source data, not a replacement for the underlying record lifecycle or ACL model. The appropriate response is: 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. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

Incorrect Answers

A:

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: Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

B:

Check instance URL and identity, release family, data sensitivity, clone schedule, environment role, and promotion approval. This evidence is relevant to Instance lifecycle and environment separation, not the most diagnostic first check for this failure. Examine: Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

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 data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

Question 179

A developer adds an application-specific setting but stores it in an unrelated global property used by other workflows. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The desired behavior changes in the intended scope and unchanged applications continue operating with known property values.
  2. The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated.
  3. The individual sees the desired columns or controls while other users retain their intended shared configuration and security.
  4. The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations.

Explanation

Correct Answer

A:

The desired behavior changes in the intended scope and unchanged applications continue operating with known property values. System properties can have broad platform effects; undocumented edits and guesswork are not a safe substitute for release-specific guidance. Scenario: A developer adds an application-specific setting but stores it in an unrelated global property used by other workflows.

Incorrect Answers

B:

The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. This result would support CMDB Identification and Reconciliation Engine source trust, not the specific outcome required in the case. The relevant acceptance test is: The desired behavior changes in the intended scope and unchanged applications continue operating with known property values. Scenario: A developer adds an application-specific setting but stores it in an unrelated global property used by other workflows.

C:

The individual sees the desired columns or controls while other users retain their intended shared configuration and security. This result would support Per-user list and form personalization, not the specific outcome required in the case. The relevant acceptance test is: The desired behavior changes in the intended scope and unchanged applications continue operating with known property values. Scenario: A developer adds an application-specific setting but stores it in an unrelated global property used by other workflows.

D:

The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations. This result would support Application installation and plugin activation preflight, not the specific outcome required in the case. The relevant acceptance test is: The desired behavior changes in the intended scope and unchanged applications continue operating with known property values. Scenario: A developer adds an application-specific setting but stores it in an unrelated global property used by other workflows.

Question 180

An approval waits indefinitely after the approver becomes inactive and no escalation branch exists. Which configuration or administrative response BEST addresses the primary issue?

  1. Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation.
  2. 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.
  3. Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment.
  4. 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.

Explanation

Correct Answer

C:

Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Waiting for approval is a durable lifecycle state; successful notification delivery and final approval are separate events. Verify prerequisites with: Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.

Incorrect Answers

A:

Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation. This approach instead addresses Workflow Studio trigger and action design. A Flow must have matching triggers and properly mapped actions; an inactive flow or false condition will not run merely because it exists. The targeted response is: Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.

B:

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. This approach instead addresses Virtual Agent human handoff and fallback. A chat session ending without a supported answer is not a successfully completed service request; escalation must be observable. The targeted response is: Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.

D:

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 an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. Scenario: An approval waits indefinitely after the approver becomes inactive and no escalation branch exists.

ServiceNow Certified System Administrator (CSA) Practice Tests