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 35

Question 340

A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The risk exception is authorized and expires or is remediated on schedule; unresolved critical findings remain visible to owners.
  2. The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows.
  3. A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked.
  4. UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors.

Explanation

Correct Answer

B:

The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. Scheduled imports require data quality, monitoring and cleanup as well as a timer; large or overlapping batches can harm platform performance. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.

Incorrect Answers

A:

The risk exception is authorized and expires or is remediated on schedule; unresolved critical findings remain visible to owners. This result would support Security Center evidence and posture exception control, not the specific outcome required in the case. The relevant acceptance test is: The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.

C:

A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. This result would support ACL debugging of roles conditions and scripts, not the specific outcome required in the case. The relevant acceptance test is: The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.

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: The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.

Question 341

A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources. 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. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.
  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 UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view.

Explanation

Correct Answer

B:

Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. Verify prerequisites with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

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: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

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 approach instead addresses Table-level versus field-level access controls. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. The targeted response is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

D:

Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view. This approach instead addresses UI Policy actions for conditional field behavior. UI Policies guide form behavior; form presentation alone does not enforce security or guarantee validation of integrations and imported data. The targeted response is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

Question 342

A catalog task is closed while the requested item remains Waiting for approval and no owner can explain the mismatch. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval.
  2. Search results lead to the current approved article, and the superseded instructions no longer mislead requesters.
  3. The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions.
  4. The record form shows only legitimately related child records, with unchanged link integrity when a child is edited.

Explanation

Correct Answer

C:

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 catalog task is closed while the requested item remains Waiting for approval and no owner can explain the mismatch.

Incorrect Answers

A:

The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval. This result would support Flow approvals and wait-for-condition boundaries, 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 catalog task is closed while the requested item remains Waiting for approval and no owner can explain the mismatch.

B:

Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. This result would support Knowledge article review, validity and version lifecycle, 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 catalog task is closed while the requested item remains Waiting for approval and no owner can explain the mismatch.

D:

The record form shows only legitimately related child records, with unchanged link integrity when a child is edited. This result would support Related lists and record relationships, 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 catalog task is closed while the requested item remains Waiting for approval and no owner can explain the mismatch.

Question 343

An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data.
  2. Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs.
  3. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  4. Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior.

Explanation

Correct Answer

B:

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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

Incorrect Answers

A:

Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. This evidence is relevant to CMDB class hierarchy and CI record modeling, not the most diagnostic first check for this failure. Examine: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

C:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This evidence is relevant to Table extension and inherited task fields, not the most diagnostic first check for this failure. Examine: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

D:

Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. This evidence is relevant to Catalog item reference qualifier and eligibility, not the most diagnostic first check for this failure. Examine: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

Question 344

An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  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. One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue.
  3. 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.
  4. Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history.
  5. Check instance URL and identity, release family, data sensitivity, clone schedule, environment role, and promotion approval.

Explanation

Correct Answers

C:

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. 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. Verify prerequisites with: Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. Scenario: An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates.

D:

Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. 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 appropriate response is: 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. Scenario: An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates.

Incorrect Answers

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. This step may apply to Platform task and service management capabilities but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. Scenario: An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates.

B:

One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue. 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: 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. Together with: Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. Scenario: An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates.

E:

Check instance URL and identity, release family, data sensitivity, clone schedule, environment role, and promotion approval. This step may apply to Instance lifecycle and environment separation but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect the navigator's active application, All menu search, module visibility, available roles, favorite target, and navigation history. Scenario: An analyst repeatedly opens the same assigned work list and asks for a quick personal shortcut without changing access for teammates.

Question 345

Two client-side policies alternately set a field mandatory and optional and agents see inconsistent behavior. Which configuration or administrative response BEST addresses the primary issue?

  1. Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations.
  2. Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout.
  3. Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement.
  4. Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation.

Explanation

Correct Answer

D:

Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation. Conditional presentation helps users but does not alone enforce security or data integrity for imports and APIs. Verify prerequisites with: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: Two client-side policies alternately set a field mandatory and optional and agents see inconsistent behavior.

Incorrect Answers

A:

Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. This approach instead addresses Elevated security administration and role boundaries. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. The targeted response is: Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation. Scenario: Two client-side policies alternately set a field mandatory and optional and agents see inconsistent behavior.

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: Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation. Scenario: Two client-side policies alternately set a field mandatory and optional and agents see inconsistent behavior.

C:

Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. This approach instead addresses Trend indicators versus transactional reports. A current count is a point-in-time measure; a trend requires consistent observations and the same measurement definition over time. The targeted response is: Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation. Scenario: Two client-side policies alternately set a field mandatory and optional and agents see inconsistent behavior.

Question 346

An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions.
  2. Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior.
  3. Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions.
  4. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.

Explanation

Correct Answer

B:

Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Reference qualifiers filter choices for usability and data correctness but do not grant or replace table ACLs. The appropriate response is: Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

Incorrect Answers

A:

Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. This evidence is relevant to Record producer versus catalog item selection, not the most diagnostic first check for this failure. Examine: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

C:

Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions. This evidence is relevant to Service Catalog item variables and validation, not the most diagnostic first check for this failure. Examine: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

D:

Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. This evidence is relevant to Reference fields and display values in the data dictionary, not the most diagnostic first check for this failure. Examine: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

Question 347

A transform map points to the Incident table when the file actually contains asset inventory records. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Resolve imported reference values and apply documented transform scripts only when ordinary field mapping is insufficient, with safe handling of absent targets.
  2. 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.
  3. Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns.
  4. All permitted entry paths enforce actual integrity and access requirements, while client interfaces remain intuitive.
  5. Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.

Explanation

Correct Answers

B:

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: A transform map points to the Incident table when the file actually contains asset inventory records.

E:

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: A transform map points to the Incident table when the file actually contains asset inventory records.

Incorrect Answers

A:

Resolve imported reference values and apply documented transform scripts only when ordinary field mapping is insufficient, with safe handling of absent targets. This step may apply to Import reference resolution and transformation scripting 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: A transform map points to the Incident table when the file actually contains asset inventory records.

C:

Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. 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: A transform map points to the Incident table when the file actually contains asset inventory records.

D:

All permitted entry paths enforce actual integrity and access requirements, while client interfaces remain intuitive. This step may apply to UI Policy versus server-side data enforcement 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: A transform map points to the Incident table when the file actually contains asset inventory records.

Question 348

A notification template includes a sensitive field that should not appear in messages sent to external requesters. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect captured customer updates, excluded data records, local target changes, preview/commit logs, post-deployment data requirements and rollback plan.
  2. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.
  3. Inspect notification active state, table, conditions, recipient resolution, event source, template, user preferences and email logs.
  4. Review indicator/report source, filter conditions, dashboard permissions, viewer roles, date range, and refresh behavior.

Explanation

Correct Answer

C:

Inspect notification active state, table, conditions, recipient resolution, event source, template, user preferences and email logs. A notification requires a matching trigger and recipient as well as a delivery path; saving its record does not itself send email. The appropriate response is: Configure notification conditions, recipients, and message content against the correct table/event with clear suppression and access boundaries, then test actual delivery. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

Incorrect Answers

A:

Inspect captured customer updates, excluded data records, local target changes, preview/commit logs, post-deployment data requirements and rollback plan. This evidence is relevant to Update set exclusions and collision resolution, not the most diagnostic first check for this failure. Examine: Inspect notification active state, table, conditions, recipient resolution, event source, template, user preferences and email logs. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

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 notification active state, table, conditions, recipient resolution, event source, template, user preferences and email logs. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

D:

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 notification active state, table, conditions, recipient resolution, event source, template, user preferences and email logs. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

Question 349

A newly created subflow returns no status because its output variable was never assigned before completion. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.
  2. Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history.
  3. Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases.
  4. Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design.

Explanation

Correct Answer

C:

Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. A subflow is reusable only when its contract and permissions are explicit; copying a flow's trigger assumptions into a shared subflow creates brittle coupling. The appropriate response is: Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

Incorrect Answers

A:

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 subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

B:

Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. This evidence is relevant to Instance properties and scoped configuration control, not the most diagnostic first check for this failure. Examine: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

D:

Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. This evidence is relevant to Workflow Studio debugging and Run As privileges, not the most diagnostic first check for this failure. Examine: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

Question 350

A high-priority incident fires an outbound integration twice because two rules emit the same event on state change. Which configuration or administrative response BEST addresses the primary issue?

  1. Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths.
  2. Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access.
  3. Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns.
  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:

Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. Verify prerequisites with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

Incorrect Answers

A:

Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths. This approach instead addresses Client script versus Business Rule and API persistence. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. The targeted response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

B:

Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access. This approach instead addresses Client server scripting with GlideAjax and scoped APIs. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. The targeted response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

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: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

ServiceNow Certified System Administrator (CSA) Practice Tests