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 3

Question 20

A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions.
  2. The script reads or changes only intended records with approved permission boundaries and predictable performance.
  3. One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications.
  4. The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup.

Explanation

Correct Answer

B:

The script reads or changes only intended records with approved permission boundaries and predictable performance. GlideRecord is a server-side record API; code correctness and secure user-level data access are separate concerns requiring enforcement. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.

Incorrect Answers

A:

Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. This result would support CMDB health completeness correctness and relationship audits, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.

C:

One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications. This result would support Business Rule recursion and idempotent side effects, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.

D:

The form receives only authorized and bounded server results, handles errors visibly, and remains responsive during lookup. This result would support Client server scripting with GlideAjax and scoped APIs, not the specific outcome required in the case. The relevant acceptance test is: The script reads or changes only intended records with approved permission boundaries and predictable performance. Scenario: A developer accepts a user-supplied sys_id and updates a restricted record without verifying the authenticated caller's entitlement.

Question 21

An accessibility reviewer finds the new theme makes mandatory field markers difficult to distinguish. Which configuration or administrative response BEST addresses the primary issue?

  1. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  2. Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance.
  3. 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.
  4. Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type.

Explanation

Correct Answer

C:

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. Branding surfaces can be configured separately across platform experiences; changing a logo or theme does not modify business rules or application data. Verify prerequisites with: Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. Scenario: An accessibility reviewer finds the new theme makes mandatory field markers difficult to distinguish.

Incorrect Answers

A:

Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. This approach instead addresses Per-user list and form personalization. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The targeted response is: 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. Scenario: An accessibility reviewer finds the new theme makes mandatory field markers difficult to distinguish.

B:

Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance. This approach instead addresses Application installation and plugin activation preflight. Activating a plugin may introduce tables, roles and configuration; it is not equivalent to adding a harmless navigation favorite. The targeted response is: 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. Scenario: An accessibility reviewer finds the new theme makes mandatory field markers difficult to distinguish.

D:

Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. This approach instead addresses Dictionary overrides on extended tables. An inherited field may have per-table overrides; editing the parent entry can affect every child table unexpectedly. The targeted response is: 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. Scenario: An accessibility reviewer finds the new theme makes mandatory field markers difficult to distinguish.

Question 22

The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Check tag applicability, record/table access, saved filter ownership, sharing settings, and list condition accuracy.
  2. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.
  3. Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence.
  4. Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases.

Explanation

Correct Answer

C:

Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. The appropriate response is: Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

Incorrect Answers

A:

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 entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

B:

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: Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

D:

Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. This evidence is relevant to Reusable subflows and defined input output contracts, not the most diagnostic first check for this failure. Examine: Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence. Scenario: The team drafts a new Virtual Agent topic but wonders why employees cannot invoke it before publishing it.

Question 23

A user import includes manager usernames but the transform attempts to store plain text in a manager reference. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies.
  2. Each security obligation has a named accountable party, and customer-managed access is not incorrectly delegated to vendor hosting support.
  3. The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records.
  4. The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see.

Explanation

Correct Answer

C:

The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. External display strings do not necessarily identify reference records, and scripts can create side effects beyond a simple field map. Scenario: A user import includes manager usernames but the transform attempts to store plain text in a manager reference.

Incorrect Answers

A:

Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies. This result would support Tenant data handling and retention governance, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A user import includes manager usernames but the transform attempts to store plain text in a manager reference.

B:

Each security obligation has a named accountable party, and customer-managed access is not incorrectly delegated to vendor hosting support. This result would support Shared responsibility between ServiceNow and customer administrators, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A user import includes manager usernames but the transform attempts to store plain text in a manager reference.

D:

The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. This result would support Next Experience application navigation and favorites, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A user import includes manager usernames but the transform attempts to store plain text in a manager reference.

Question 24

A team assumes moving a freeform board card to Done automatically closes an Incident record. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  2. Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects.
  3. Review indicator/report source, filter conditions, dashboard permissions, viewer roles, date range, and refresh behavior.
  4. Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership.

Explanation

Correct Answer

B:

Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Visual Task Boards can be collaborative displays; board/card configuration determines whether a move changes a task field or only planning metadata. The appropriate response is: Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Scenario: A team assumes moving a freeform board card to Done automatically closes an Incident record.

Incorrect Answers

A:

Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. This evidence is relevant to Scoped application permissions and cross-scope access, not the most diagnostic first check for this failure. Examine: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: A team assumes moving a freeform board card to Done automatically closes an Incident record.

C:

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 VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: A team assumes moving a freeform board card to Done automatically closes an Incident record.

D:

Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. This evidence is relevant to List filter conditions and breadcrumb logic, not the most diagnostic first check for this failure. Examine: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: A team assumes moving a freeform board card to Done automatically closes an Incident record.

Question 25

An expensive laptop RITM is fulfilled before its manager approval condition has evaluated. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect trigger table and changes, execution context, action configuration, input mappings, flow activation state, and run history.
  2. The desired behavior changes in the intended scope and unchanged applications continue operating with known property values.
  3. Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights.
  4. Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable.
  5. Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior.

Explanation

Correct Answers

D:

Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. REQ, RITM and catalog task are distinct records with different scopes; notifying a manager does not imply a requested item was approved. Verify prerequisites with: Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. Scenario: An expensive laptop RITM is fulfilled before its manager approval condition has evaluated.

E:

Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. REQ, RITM and catalog task are distinct records with different scopes; notifying a manager does not imply a requested item was approved. The appropriate response is: Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. Scenario: An expensive laptop RITM is fulfilled before its manager approval condition has evaluated.

Incorrect Answers

A:

Inspect trigger table and changes, execution context, action configuration, input mappings, flow activation state, and run history. This step may apply to Workflow Studio trigger and action design but is not one of the complementary requirements in this case. The intended pair is: Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. Together with: Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. Scenario: An expensive laptop RITM is fulfilled before its manager approval condition has evaluated.

B:

The desired behavior changes in the intended scope and unchanged applications continue operating with known property values. This step may apply to Instance properties and scoped configuration control but is not one of the complementary requirements in this case. The intended pair is: Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. Together with: Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. Scenario: An expensive laptop RITM is fulfilled before its manager approval condition has evaluated.

C:

Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. This step may apply to Workflow Studio debugging and Run As privileges but is not one of the complementary requirements in this case. The intended pair is: Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. Together with: Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. Scenario: An expensive laptop RITM is fulfilled before its manager approval condition has evaluated.

Question 26

A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  2. Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership.
  3. 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.
  4. Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies.
  5. The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval.

Explanation

Correct Answers

B:

Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. A CMDB health score is only as meaningful as the selected rules and data sources; dashboards alone do not repair faulty CI relationships. The appropriate response is: Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

D:

Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. A CMDB health score is only as meaningful as the selected rules and data sources; dashboards alone do not repair faulty CI relationships. Verify prerequisites with: Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

Incorrect Answers

A:

Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. This step may apply to Scoped application permissions and cross-scope access but is not one of the complementary requirements in this case. The intended pair is: Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. Together with: Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

C:

Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. This step may apply to CMDB Identification and Reconciliation Engine source trust but is not one of the complementary requirements in this case. The intended pair is: Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. Together with: Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

E:

The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval. This step may apply to Flow approvals and wait-for-condition boundaries but is not one of the complementary requirements in this case. The intended pair is: Improve CMDB trust using health checks and source remediation for duplicate, stale or incomplete CI data rather than presenting a dashboard score as proof of accurate dependencies. Together with: Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

Question 27

A low-trust spreadsheet import overwrites the authoritative device owner supplied by the inventory source. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. An application incident can be traced through correct service relationships to affected service offerings and stakeholders.
  2. The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated.
  3. A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality.
  4. Each CI has a consistent class and attributable relationships that support intended impact analysis.

Explanation

Correct Answer

B:

The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. 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. Scenario: A low-trust spreadsheet import overwrites the authoritative device owner supplied by the inventory source.

Incorrect Answers

A:

An application incident can be traced through correct service relationships to affected service offerings and stakeholders. This result would support Common Service Data Model service relationships, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A low-trust spreadsheet import overwrites the authoritative device owner supplied by the inventory source.

C:

A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality. This result would support Update set creation completion and ordered promotion, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A low-trust spreadsheet import overwrites the authoritative device owner supplied by the inventory source.

D:

Each CI has a consistent class and attributable relationships that support intended impact analysis. This result would support CMDB class hierarchy and CI record modeling, not the specific outcome required in the case. The relevant acceptance test is: The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. Scenario: A low-trust spreadsheet import overwrites the authoritative device owner supplied by the inventory source.

Question 28

A form requires Asset tag but an import inserts empty Asset tag values because only a UI Policy enforces it. 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 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.
  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. Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs.

Explanation

Correct Answer

D:

Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Client-side policy alone does not protect API writes or data integrity; security and mandatory validation must be enforced at the appropriate server boundary. Verify prerequisites with: Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. Scenario: A form requires Asset tag but an import inserts empty Asset tag values because only a UI Policy enforces it.

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: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: A form requires Asset tag but an import inserts empty Asset tag values because only a UI Policy enforces it.

B:

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: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: A form requires Asset tag but an import inserts empty Asset tag values because only a UI Policy enforces it.

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: Apply UI Policies for visual guidance and appropriate server-side rules, data policies, ACLs or business validation when the requirement must hold across imports or APIs. Scenario: A form requires Asset tag but an import inserts empty Asset tag values because only a UI Policy enforces it.

Question 29

A user expects a related list on a configuration item form to expose all child records even when those records are ACL-protected. Which configuration or administrative response BEST addresses the primary issue?

  1. 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.
  2. Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records.
  3. 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. Use tags and saved filters for organizing or retrieving records while setting ownership and sharing appropriately; do not treat a label as a role or ACL.

Explanation

Correct Answer

B:

Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. A related list is a query-backed view of associated records; it does not inherently store copies of all child rows on the parent. Verify prerequisites with: Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration. Scenario: A user expects a related list on a configuration item form to expose all child records even when those records are ACL-protected.

Incorrect Answers

A:

Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. This approach instead addresses CMDB Identification and Reconciliation Engine source trust. Identification and reconciliation distinguish an existing CI from a new one and govern conflicting data sources; a generic coalesce map alone may be insufficient for CMDB integrity. The targeted response is: Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. Scenario: A user expects a related list on a configuration item form to expose all child records even when those records are ACL-protected.

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: Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. Scenario: A user expects a related list on a configuration item form to expose all child records even when those records are ACL-protected.

D:

Use tags and saved filters for organizing or retrieving records while setting ownership and sharing appropriately; do not treat a label as a role or ACL. This approach instead addresses List tags and saved filter sharing. Tags organize records and filters select records; neither overrides read permissions nor creates task assignment automatically. The targeted response is: Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. Scenario: A user expects a related list on a configuration item form to expose all child records even when those records are ACL-protected.

Question 30

A script in one scoped application calls a protected API in another scope and receives a cross-scope access error. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  2. 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.
  3. The correct trigger starts one flow execution and approved actions modify the intended records without unrelated updates.
  4. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.
  5. Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs.

Explanation

Correct Answers

A:

Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The appropriate 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 script in one scoped application calls a protected API in another scope and receives a cross-scope access error.

D:

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 script in one scoped application calls a protected API in another scope and receives a cross-scope access error.

Incorrect Answers

B:

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 step may apply to Table-level versus field-level access controls but is not one of the complementary requirements in this case. The intended pair is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A script in one scoped application calls a protected API in another scope and receives a cross-scope access error.

C:

The correct trigger starts one flow execution and approved actions modify the intended records without unrelated updates. This step may apply to Workflow Studio trigger and action design but is not one of the complementary requirements in this case. The intended pair is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A script in one scoped application calls a protected API in another scope and receives a cross-scope access error.

E:

Inspect elevated privilege state, role grants, security ACL changes, approval record, active session and change audit logs. This step may apply to Elevated security administration and role boundaries but is not one of the complementary requirements in this case. The intended pair is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A script in one scoped application calls a protected API in another scope and receives a cross-scope access error.

ServiceNow Certified System Administrator (CSA) Practice Tests