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 76

Question 750

A newly created subflow returns no status because its output variable was never assigned before completion. 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 requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response.
  3. The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.
  4. Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names.

Explanation

Correct Answer

D:

Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. A subflow is reusable only when its contract and permissions are explicit; copying a flow's trigger assumptions into a shared subflow creates brittle coupling. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

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: Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

B:

The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. This result would support Virtual Agent topic routing and conversation state, not the specific outcome required in the case. The relevant acceptance test is: Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

C:

The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step. This result would support Workflow Studio debugging and Run As privileges, not the specific outcome required in the case. The relevant acceptance test is: Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.

Question 751

An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.
  2. Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data.
  3. Authorized users read or write only permitted table rows and fields, and unauthorized API or form access is denied.
  4. Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied.

Explanation

Correct Answer

D:

Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

Incorrect Answers

A:

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: Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

B:

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: Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

C:

Authorized users read or write only permitted table rows and fields, and unauthorized API or form access is denied. This result would support Table-level versus field-level access controls, not the specific outcome required in the case. The relevant acceptance test is: Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

Question 752

Virtual Agent returns an internal-only knowledge article to a contractor who lacks its user criteria. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence.
  2. Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record.
  3. Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience.
  4. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.

Explanation

Correct Answer

D:

Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. A Virtual Agent's conversational acknowledgment cannot substitute for a confirmed catalog order or an authorized knowledge article. The appropriate response is: Use approved Virtual Agent integrations for knowledge guidance or catalog item submission with correct authenticated context and record verification. Scenario: Virtual Agent returns an internal-only knowledge article to a contractor who lacks its user criteria.

Incorrect Answers

A:

Review entry intent, topic publication state, fallback logic, conversation variable mapping, user permissions, and transcript evidence. This evidence is relevant to Virtual Agent topic routing and conversation state, not the most diagnostic first check for this failure. Examine: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: Virtual Agent returns an internal-only knowledge article to a contractor who lacks its user criteria.

B:

Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record. This evidence is relevant to Virtual Agent human handoff and fallback, not the most diagnostic first check for this failure. Examine: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: Virtual Agent returns an internal-only knowledge article to a contractor who lacks its user criteria.

C:

Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. This evidence is relevant to Now Platform shared records and configurable applications, not the most diagnostic first check for this failure. Examine: Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: Virtual Agent returns an internal-only knowledge article to a contractor who lacks its user criteria.

Question 753

A transform coalesces on a common department name and overwrites the first matching user account. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.
  2. Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible.
  3. An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task.
  4. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.
  5. Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction.

Explanation

Correct Answers

A:

Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. The appropriate response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

D:

Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. Verify prerequisites with: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

Incorrect Answers

B:

Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. This step may apply to User group and role assignment principle of least privilege but is not one of the complementary requirements in this case. The intended pair is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Together with: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

C:

An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. This step may apply to Virtual Agent human handoff and fallback but is not one of the complementary requirements in this case. The intended pair is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Together with: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

E:

Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. This step may apply to Common Service Data Model service relationships but is not one of the complementary requirements in this case. The intended pair is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Together with: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

Question 754

A manager updates a template and expects existing closed records to be retroactively rewritten. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement.
  2. Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule.
  3. Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names.
  4. Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.
  5. Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes.

Explanation

Correct Answers

B:

Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. Verify prerequisites with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A manager updates a template and expects existing closed records to be retroactively rewritten.

E:

Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. The appropriate response is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Scenario: A manager updates a template and expects existing closed records to be retroactively rewritten.

Incorrect Answers

A:

Select history-aware analytics and explicit indicator definitions for trends, rather than claiming a one-time filtered list snapshot proves a sustained performance improvement. This step may apply to Trend indicators versus transactional reports but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A manager updates a template and expects existing closed records to be retroactively rewritten.

C:

Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. This step may apply to Reusable subflows and defined input output contracts but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A manager updates a template and expects existing closed records to be retroactively rewritten.

D:

Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. This step may apply to List versus form anatomy and record identity but is not one of the complementary requirements in this case. The intended pair is: Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. Together with: Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. Scenario: A manager updates a template and expects existing closed records to be retroactively rewritten.

Question 755

A team disputes a posture alert and refuses to collect configuration evidence that could show whether it is false positive. Which configuration or administrative response BEST addresses the primary issue?

  1. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.
  2. 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.
  3. Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome.
  4. 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.

Explanation

Correct Answer

A:

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: A team disputes a posture alert and refuses to collect configuration evidence that could show whether it is false positive.

Incorrect Answers

B:

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: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Scenario: A team disputes a posture alert and refuses to collect configuration evidence that could show whether it is false positive.

C:

Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. This approach instead addresses Virtual Agent topic routing and conversation state. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. The targeted response is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Scenario: A team disputes a posture alert and refuses to collect configuration evidence that could show whether it is false positive.

D:

Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. This approach instead addresses Table-level versus field-level access controls. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. The targeted response is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Scenario: A team disputes a posture alert and refuses to collect configuration evidence that could show whether it is false positive.

Question 756

Users report that one knowledge search result is forbidden even though the article title is visible to them. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states.
  2. The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details.
  3. Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior.
  4. Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context.
  5. Publish a knowledge article through its supported draft/review/publish workflow, assigning it to the right knowledge base and checking article/user criteria for the intended audience.

Explanation

Correct Answers

A:

Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states. Knowledge feedback guides the content lifecycle; voting an article Helpful does not update the underlying process or grant requester access. Verify prerequisites with: Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. Scenario: Users report that one knowledge search result is forbidden even though the article title is visible to them.

D:

Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. Knowledge feedback guides the content lifecycle; voting an article Helpful does not update the underlying process or grant requester access. The appropriate response is: Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states. Scenario: Users report that one knowledge search result is forbidden even though the article title is visible to them.

Incorrect Answers

B:

The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. This step may apply to Notification trigger recipient and content configuration but is not one of the complementary requirements in this case. The intended pair is: Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states. Together with: Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. Scenario: Users report that one knowledge search result is forbidden even though the article title is visible to them.

C:

Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. This step may apply to Catalog item reference qualifier and eligibility but is not one of the complementary requirements in this case. The intended pair is: Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states. Together with: Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. Scenario: Users report that one knowledge search result is forbidden even though the article title is visible to them.

E:

Publish a knowledge article through its supported draft/review/publish workflow, assigning it to the right knowledge base and checking article/user criteria for the intended audience. This step may apply to Knowledge base article publication and access but is not one of the complementary requirements in this case. The intended pair is: Use knowledge search telemetry and actionable reader feedback to improve article findability, ownership and correctness rather than hiding complaints or changing unrelated incident states. Together with: Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context. Scenario: Users report that one knowledge search result is forbidden even though the article title is visible to them.

Question 757

A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions.
  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. Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data.
  4. Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible.
  5. One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications.

Explanation

Correct Answers

A:

Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Roles control capabilities while groups often organize work and confer roles; assignment to a task group does not inherently grant all administrator privileges. The appropriate response is: Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.

D:

Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Roles control capabilities while groups often organize work and confer roles; assignment to a task group does not inherently grant all administrator privileges. Verify prerequisites with: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.

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: Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Together with: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.

C:

Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. This step may apply to CMDB class hierarchy and CI record modeling but is not one of the complementary requirements in this case. The intended pair is: Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Together with: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.

E:

One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications. This step may apply to Business Rule recursion and idempotent side effects but is not one of the complementary requirements in this case. The intended pair is: Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Together with: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.

Question 758

Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs.
  2. Represent configuration items in appropriate CMDB classes and validate core attributes and relationships rather than using generic text records for every device and service.
  3. Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation.
  4. The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction.
  5. 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.

Explanation

Correct Answers

A:

Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Identification and reconciliation distinguish an existing CI from a new one and govern conflicting data sources; a generic coalesce map alone may be insufficient for CMDB integrity. The appropriate response is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Scenario: Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB.

E:

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. 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. Verify prerequisites with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB.

Incorrect Answers

B:

Represent configuration items in appropriate CMDB classes and validate core attributes and relationships rather than using generic text records for every device and service. This step may apply to CMDB class hierarchy and CI record modeling but is not one of the complementary requirements in this case. The intended pair is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB.

C:

Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. This step may apply to Shared responsibility between ServiceNow and customer administrators but is not one of the complementary requirements in this case. The intended pair is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB.

D:

The form starts in the appropriate state and transitions consistently as the controlling value changes in either direction. This step may apply to UI Policy onLoad and reverse behavior controls but is not one of the complementary requirements in this case. The intended pair is: Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. Together with: Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs. Scenario: Two discovery connectors report the same server under different hostnames and create duplicate CIs in the CMDB.

Question 759

An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions.
  2. Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes.
  3. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  4. Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context.

Explanation

Correct Answer

C:

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: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

Incorrect Answers

A:

Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. This evidence is relevant to User group and role assignment principle of least privilege, not the most diagnostic first check for this failure. Examine: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

B:

Check target table/view, template field mappings, user permissions, applied defaults, and post-template value changes. This evidence is relevant to Form templates and controlled record creation, not the most diagnostic first check for this failure. Examine: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

D:

Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. This evidence is relevant to Table-level versus field-level access controls, not the most diagnostic first check for this failure. Examine: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: An integration works for an admin during testing but fails for a routine agent because only scope policy, not the user's ACL, was considered.

Question 760

An operator presents one day of reduced backlog as proof the weekly service level objective is met. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated.
  2. Dragging a data-driven card produces the intended authorized record state/field change, while freeform boards behave according to their configured model.
  3. The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation.
  4. A selected record can be traced unambiguously from list to form and only its intended fields change after saving.

Explanation

Correct Answer

C:

The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. A current count is a point-in-time measure; a trend requires consistent observations and the same measurement definition over time. Scenario: An operator presents one day of reduced backlog as proof the weekly service level objective is met.

Incorrect Answers

A:

The correct CI is found or created once, approved sources update permitted attributes, and duplicate/untrusted values are rejected or investigated. This result would support CMDB Identification and Reconciliation Engine source trust, not the specific outcome required in the case. The relevant acceptance test is: The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. Scenario: An operator presents one day of reduced backlog as proof the weekly service level objective is met.

B:

Dragging a data-driven card produces the intended authorized record state/field change, while freeform boards behave according to their configured model. This result would support Visual Task Board data-driven and freeform handling, not the specific outcome required in the case. The relevant acceptance test is: The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. Scenario: An operator presents one day of reduced backlog as proof the weekly service level objective is met.

D:

A selected record can be traced unambiguously from list to form and only its intended fields change after saving. This result would support List versus form anatomy and record identity, not the specific outcome required in the case. The relevant acceptance test is: The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. Scenario: An operator presents one day of reduced backlog as proof the weekly service level objective is met.

ServiceNow Certified System Administrator (CSA) Practice Tests