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 39

Question 380

A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability.
  2. The dashboard shows understandable and timely metrics to authorized viewers without revealing fields they cannot read.
  3. Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally.
  4. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.
  5. Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership.

Explanation

Correct Answers

A:

Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. The appropriate response is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

C:

Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. Verify prerequisites with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

Incorrect Answers

B:

The dashboard shows understandable and timely metrics to authorized viewers without revealing fields they cannot read. This step may apply to Dashboards and Platform Analytics audience permissions but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

D:

Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. This step may apply to Audit and accountability for privileged instance operations but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

E:

Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. 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: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

Question 381

A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context.
  2. Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation.
  3. Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form.
  4. Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations.
  5. The individual sees the desired columns or controls while other users retain their intended shared configuration and security.

Explanation

Correct Answers

A:

Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. The appropriate response is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Scenario: A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it.

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. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. Verify prerequisites with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it.

Incorrect Answers

B:

Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. This step may apply to Security Center evidence and posture exception control but is not one of the complementary requirements in this case. The intended pair is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it.

D:

Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. 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: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it.

E:

The individual sees the desired columns or controls while other users retain their intended shared configuration and security. This step may apply to Per-user list and form personalization but is not one of the complementary requirements in this case. The intended pair is: Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. Together with: Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. Scenario: A developer makes a sensitive field invisible on the form and claims that unprivileged API callers cannot fetch it.

Question 382

The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task.
  2. A user receives an authorized knowledge result or a confirmed catalog request number, and a failed submission is explicitly reported.
  3. The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records.
  4. The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response.

Explanation

Correct Answer

D:

The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

Incorrect Answers

A:

An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. This result would support Virtual Agent human handoff and fallback, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

B:

A user receives an authorized knowledge result or a confirmed catalog request number, and a failed submission is explicitly reported. This result would support Virtual Agent integrated knowledge and catalog fulfillment, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

C:

The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. This result would support List filter conditions and breadcrumb logic, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

Question 383

A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record.
  2. Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions.
  3. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.
  4. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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 fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

C:

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 fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

D:

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 fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. Scenario: A virtual assistant loops on the same failed troubleshooting step instead of offering a human support handoff.

Question 384

A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  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. Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape.
  3. 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.
  4. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.
  5. Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts.

Explanation

Correct Answers

B:

Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. The appropriate response is: 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. Scenario: A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context.

C:

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. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. Verify prerequisites with: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context.

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 step may apply to Update set exclusions and collision resolution but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context.

D:

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: 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. Together with: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context.

E:

Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. This step may apply to UI Policy actions for conditional field behavior but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: A client onChange script tries to instantiate server-side GlideRecord and fails outside the server context.

Question 385

A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks. Which configuration or administrative response BEST addresses the primary issue?

  1. 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.
  2. Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms.
  3. 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.
  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

A:

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: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

Incorrect Answers

B:

Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms. This approach instead addresses Instance lifecycle and environment separation. ServiceNow instances have separate data/configuration state; personal developer or test instances should not be treated as production replicas without controlled clones and access. The targeted response is: 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: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

C:

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: 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: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

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 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: A new agent cannot locate the Incident module from the Next Experience interface and searches only browser bookmarks.

Question 386

A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records.
  2. The form shows context-appropriate actions and editable fields, while invalid or unauthorized data modifications remain blocked server-side.
  3. The intended users see the approved form field order while role-based access and record data remain intact.
  4. A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.

Explanation

Correct Answer

A:

The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

Incorrect Answers

B:

The form shows context-appropriate actions and editable fields, while invalid or unauthorized data modifications remain blocked server-side. This result would support Advanced form configuration and conditional display, not the specific outcome required in the case. The relevant acceptance test is: The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

C:

The intended users see the approved form field order while role-based access and record data remain intact. This result would support Form Designer and field ordering by view, not the specific outcome required in the case. The relevant acceptance test is: The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

D:

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: The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

Question 387

A user confuses the incident number INC0012345 with the system-generated sys_id when inspecting a reference field. Which configuration or administrative response BEST addresses the primary issue?

  1. Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms.
  2. 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.
  3. Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work.
  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

B:

Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. Verify prerequisites with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A user confuses the incident number INC0012345 with the system-generated sys_id when inspecting a reference field.

Incorrect Answers

A:

Keep development, test, and production ServiceNow instances distinct and validate configuration changes in a nonproduction environment before promotion through controlled mechanisms. This approach instead addresses Instance lifecycle and environment separation. ServiceNow instances have separate data/configuration state; personal developer or test instances should not be treated as production replicas without controlled clones and access. The targeted response is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Scenario: A user confuses the incident number INC0012345 with the system-generated sys_id when inspecting a reference field.

C:

Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. This approach instead addresses Task assignment group versus individual responsibility. A task assigned to a group but not an individual is group work, not proof any specific agent owns it. The targeted response is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Scenario: A user confuses the incident number INC0012345 with the system-generated sys_id when inspecting a reference field.

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. This approach instead addresses Advanced form configuration and conditional display. Conditional presentation helps users but does not alone enforce security or data integrity for imports and APIs. The targeted response is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Scenario: A user confuses the incident number INC0012345 with the system-generated sys_id when inspecting a reference field.

Question 388

A catalog item appears to every contractor even though company policy limits the item to staff in one department. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The task proceeds only after the required decision is recorded and authorized, with rejected approvals taking the defined alternate path.
  2. A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data.
  3. One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements.
  4. Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces.

Explanation

Correct Answer

D:

Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces. Reference qualifiers filter choices for usability and data correctness but do not grant or replace table ACLs. Scenario: A catalog item appears to every contractor even though company policy limits the item to staff in one department.

Incorrect Answers

A:

The task proceeds only after the required decision is recorded and authorized, with rejected approvals taking the defined alternate path. This result would support Task approval and state workflow audit, not the specific outcome required in the case. The relevant acceptance test is: Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces. Scenario: A catalog item appears to every contractor even though company policy limits the item to staff in one department.

B:

A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. This result would support Record producer versus catalog item selection, not the specific outcome required in the case. The relevant acceptance test is: Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces. Scenario: A catalog item appears to every contractor even though company policy limits the item to staff in one department.

C:

One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements. This result would support Service Catalog order guide and request structure, not the specific outcome required in the case. The relevant acceptance test is: Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces. Scenario: A catalog item appears to every contractor even though company policy limits the item to staff in one department.

Question 389

A developer changes an incident form but later discovers the updates were saved into the Default update set rather than the deployment package. 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 affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts.
  3. Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
  4. Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval.

Explanation

Correct Answer

D:

Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. Update sets track many configuration customizations, not arbitrary production business data; a named update set and preview are key controls. The appropriate response is: Capture configuration changes in the appropriate update set and promote them through controlled development, test and production preview/commit stages. Scenario: A developer changes an incident form but later discovers the updates were saved into the Default update set rather than the deployment package.

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 application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. Scenario: A developer changes an incident form but later discovers the updates were saved into the Default update set rather than the deployment package.

B:

Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. This evidence is relevant to UI Policy actions for conditional field behavior, not the most diagnostic first check for this failure. Examine: Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. Scenario: A developer changes an incident form but later discovers the updates were saved into the Default update set rather than the deployment package.

C:

Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. This evidence is relevant to Form sections and related layout configuration, not the most diagnostic first check for this failure. Examine: Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. Scenario: A developer changes an incident form but later discovers the updates were saved into the Default update set rather than the deployment package.

Question 390

A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI.
  2. Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts.
  3. Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change.
  4. Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies.

Explanation

Correct Answer

C:

Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. The appropriate response is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

Incorrect Answers

A:

Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. This evidence is relevant to UI Policy versus server-side data enforcement, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

B:

Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. This evidence is relevant to UI Policy actions for conditional field behavior, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

D:

Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. This evidence is relevant to Instance branding and portal experience settings, not the most diagnostic first check for this failure. Examine: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

ServiceNow Certified System Administrator (CSA) Practice Tests