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 86

Question 850

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

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

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

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

D:

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

Question 851

A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence. Which configuration or administrative response BEST addresses the primary issue?

  1. Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance.
  2. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.
  3. Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result.
  4. Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls.

Explanation

Correct Answer

D:

Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Security dashboards organize findings and help prioritization; they do not replace system ACLs, authentication, or independent verification of a fix. Verify prerequisites with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

Incorrect Answers

A:

Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. This approach instead addresses Shared responsibility between ServiceNow and customer administrators. A hosted ServiceNow service does not absolve customers of properly configured roles, ACLs and data handling; platform hosting and customer configuration are different responsibilities. The targeted response is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Scenario: A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

B:

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: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Scenario: A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

C:

Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. This approach instead addresses Knowledge article review, validity and version lifecycle. Reusing knowledge is valuable only if ownership, currency and intended audience are maintained; a search hit is not proof of current policy. The targeted response is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Scenario: A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

Question 852

An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values.
  2. The script reads or changes only intended records with approved permission boundaries and predictable performance.
  3. The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup.
  4. The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations.

Explanation

Correct Answer

C:

The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

Incorrect Answers

A:

When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This result would support UI Policy actions for conditional field behavior, not the specific outcome required in the case. The relevant acceptance test is: The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

B:

The script reads or changes only intended records with approved permission boundaries and predictable performance. This result would support GlideRecord server-side query and secure result handling, not the specific outcome required in the case. The relevant acceptance test is: The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

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 form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

Question 853

An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view.
  2. Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy.
  3. 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.
  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.
  5. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.

Explanation

Correct Answers

A:

Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Conditional presentation helps users but does not alone enforce security or data integrity for imports and APIs. The appropriate 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: An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API.

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: An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API.

Incorrect Answers

B:

Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. This step may apply to List tags and saved filter sharing but is not one of the complementary requirements in this case. The intended pair 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. Together with: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API.

C:

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 step may apply to List filter conditions and breadcrumb logic but is not one of the complementary requirements in this case. The intended pair 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. Together with: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API.

E:

The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning. This step may apply to Configurable form and workspace layout changes but is not one of the complementary requirements in this case. The intended pair 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. Together with: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: An administrator hides a sensitive field and incorrectly concludes users could never retrieve its value through an API.

Question 854

An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation.
  2. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.
  3. The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person.
  4. Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls.
  5. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.

Explanation

Correct Answers

A:

Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Accepting a known exception is a governance decision, not evidence the security configuration meets the baseline. The appropriate response is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

E:

Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Accepting a known exception is a governance decision, not evidence the security configuration meets the baseline. Verify prerequisites with: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

Incorrect Answers

B:

Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. This step may apply to Reference fields and display values in the data dictionary but is not one of the complementary requirements in this case. The intended pair is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Together with: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

C:

The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person. This step may apply to Task assignment group versus individual responsibility but is not one of the complementary requirements in this case. The intended pair is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Together with: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

D:

Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. This step may apply to Security Center security posture triage but is not one of the complementary requirements in this case. The intended pair is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Together with: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

Question 855

A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls.
  2. Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification.
  3. Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.
  4. The record form shows only legitimately related child records, with unchanged link integrity when a child is edited.
  5. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.

Explanation

Correct Answers

A:

Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Security dashboards organize findings and help prioritization; they do not replace system ACLs, authentication, or independent verification of a fix. Verify prerequisites with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration.

B:

Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Security dashboards organize findings and help prioritization; they do not replace system ACLs, authentication, or independent verification of a fix. The appropriate response is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Scenario: A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration.

Incorrect Answers

C:

Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. This step may apply to Coalesce keys and update versus insert control but is not one of the complementary requirements in this case. The intended pair is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration.

D:

The record form shows only legitimately related child records, with unchanged link integrity when a child is edited. 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 supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration.

E:

Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. This step may apply to Security Center evidence and posture exception control but is not one of the complementary requirements in this case. The intended pair is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security reviewer sees an elevated posture warning and plans to mark it resolved without changing the underlying instance configuration.

Question 856

An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting.
  2. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  3. Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions.
  4. Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user.
  5. Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records.

Explanation

Correct Answers

B:

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: An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary.

D:

Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The appropriate 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: An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary.

Incorrect Answers

A:

Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting. This step may apply to Instance branding and portal experience settings but is not one of the complementary requirements in this case. The intended pair is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Together 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: An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary.

C:

Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. 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: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Together 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: An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary.

E:

Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. This step may apply to Core platform lists versus forms and workspaces but is not one of the complementary requirements in this case. The intended pair is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Together 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: An administrator confuses adding a column to a list for one agent with adding a new field to the data dictionary.

Question 857

A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release. Which configuration or administrative response BEST addresses the primary issue?

  1. Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience.
  2. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.
  3. Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete.
  4. Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment.

Explanation

Correct Answer

D:

Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment. System properties can have broad platform effects; undocumented edits and guesswork are not a safe substitute for release-specific guidance. Verify prerequisites with: Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. Scenario: A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

Incorrect Answers

A:

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: Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment. Scenario: A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

B:

Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. This approach instead addresses Scoped application permissions and cross-scope access. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The targeted response is: Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment. Scenario: A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

C:

Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. This approach instead addresses Plugin feature validation after activation. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. The targeted response is: Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment. Scenario: A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

Question 858

An agent changes a field back to its original value but a previously mandatory field remains required because reverse behavior was disabled. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction.
  2. All permitted entry paths enforce actual integrity and access requirements, while client interfaces remain intuitive.
  3. The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results.
  4. When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values.

Explanation

Correct Answer

A:

The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. Scenario: An agent changes a field back to its original value but a previously mandatory field remains required because reverse behavior was disabled.

Incorrect Answers

B:

All permitted entry paths enforce actual integrity and access requirements, while client interfaces remain intuitive. This result would support UI Policy versus server-side data enforcement, not the specific outcome required in the case. The relevant acceptance test is: The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction. Scenario: An agent changes a field back to its original value but a previously mandatory field remains required because reverse behavior was disabled.

C:

The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results. This result would support Reference fields and display values in the data dictionary, not the specific outcome required in the case. The relevant acceptance test is: The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction. Scenario: An agent changes a field back to its original value but a previously mandatory field remains required because reverse behavior was disabled.

D:

When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This result would support UI Policy actions for conditional field behavior, not the specific outcome required in the case. The relevant acceptance test is: The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction. Scenario: An agent changes a field back to its original value but a previously mandatory field remains required because reverse behavior was disabled.

Question 859

A form button remains visible to users who lack permission to carry out the associated server-side update. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view.
  2. Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions.
  3. Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.
  4. Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy.

Explanation

Correct Answer

A:

Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Conditional presentation helps users but does not alone enforce security or data integrity for imports and APIs. The appropriate 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: A form button remains visible to users who lack permission to carry out the associated server-side update.

Incorrect Answers

B:

Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. This evidence is relevant to Unified navigation between workspaces and platform views, not the most diagnostic first check for this failure. Examine: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: A form button remains visible to users who lack permission to carry out the associated server-side update.

C:

Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. This evidence is relevant to List versus form anatomy and record identity, not the most diagnostic first check for this failure. Examine: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: A form button remains visible to users who lack permission to carry out the associated server-side update.

D:

Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy. This evidence is relevant to List tags and saved filter sharing, not the most diagnostic first check for this failure. Examine: Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. Scenario: A form button remains visible to users who lack permission to carry out the associated server-side update.

Question 860

A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs.
  2. 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.
  3. Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns.
  4. Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls.
  5. The user navigates from the authorized list to the intended form or workspace and changes the correct record with an audit trail.

Explanation

Correct Answers

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 Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

D:

Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The appropriate 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 Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

Incorrect Answers

A:

Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs. This step may apply to Business Rule timing and before after async display behavior but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

B:

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 step may apply to Client script versus Business Rule and API persistence but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

E:

The user navigates from the authorized list to the intended form or workspace and changes the correct record with an audit trail. This step may apply to Core platform lists versus forms and workspaces but is not one of the complementary requirements in this case. The intended pair is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Together with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

ServiceNow Certified System Administrator (CSA) Practice Tests