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 8

Question 70

Incident impact is overreported because every application server is marked as a separate business service without dependency links. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction.
  2. Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.
  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. Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact.
  5. A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality.

Explanation

Correct Answers

A:

Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. CSDM provides consistent service modeling conventions, not a single generic CI class into which all offerings and applications should be placed. The appropriate response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

D:

Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. CSDM provides consistent service modeling conventions, not a single generic CI class into which all offerings and applications should be placed. Verify prerequisites with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

Incorrect Answers

B:

Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. This step may apply to Import set staging and transform-map field mappings but is not one of the complementary requirements in this case. The intended pair is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Together with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

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: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Together with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

E:

A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality. This step may apply to Update set creation completion and ordered promotion but is not one of the complementary requirements in this case. The intended pair is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Together with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

Question 71

A request form displays one department name while the underlying department reference points to a retired record. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review indicator/report source, filter conditions, dashboard permissions, viewer roles, date range, and refresh behavior.
  2. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.
  3. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  4. Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes.

Explanation

Correct Answer

B:

Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. A ServiceNow reference is stored as a record identifier, while users commonly see the referenced record's display value. The appropriate response is: Define a reference field to a suitable target table and validate stored sys_id and display-value behavior, rather than treating a text label as a reliable relationship key. Scenario: A request form displays one department name while the underlying department reference points to a retired record.

Incorrect Answers

A:

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 reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. Scenario: A request form displays one department name while the underlying department reference points to a retired record.

C:

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 reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. Scenario: A request form displays one department name while the underlying department reference points to a retired record.

D:

Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. This evidence is relevant to Dictionary attributes and field type integrity, not the most diagnostic first check for this failure. Examine: Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. Scenario: A request form displays one department name while the underlying department reference points to a retired record.

Question 72

An administrator disables all Business Rules during troubleshooting instead of identifying the condition causing repeated writes. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls.
  2. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  3. Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval.
  4. Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form.

Explanation

Correct Answer

A:

Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The appropriate response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: An administrator disables all Business Rules during troubleshooting instead of identifying the condition causing repeated writes.

Incorrect Answers

B:

Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. This evidence is relevant to Audit and accountability for privileged instance operations, not the most diagnostic first check for this failure. Examine: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: An administrator disables all Business Rules during troubleshooting instead of identifying the condition causing repeated writes.

C:

Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. This evidence is relevant to Update set creation completion and ordered promotion, not the most diagnostic first check for this failure. Examine: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: An administrator disables all Business Rules during troubleshooting instead of identifying the condition causing repeated writes.

D:

Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. This evidence is relevant to Client script versus Business Rule and API persistence, not the most diagnostic first check for this failure. Examine: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: An administrator disables all Business Rules during troubleshooting instead of identifying the condition causing repeated writes.

Question 73

A scheduled cleanup script queries the wrong table and needs diagnostic filters before any destructive update is enabled. Which configuration or administrative response BEST addresses the primary issue?

  1. Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects.
  2. Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths.
  3. Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns.
  4. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.

Explanation

Correct Answer

A:

Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects. GlideRecord is a server-side record API; code correctness and secure user-level data access are separate concerns requiring enforcement. Verify prerequisites with: Inspect table name, field conditions, row limits, running identity, authorization checks, result count, and transaction logs. Scenario: A scheduled cleanup script queries the wrong table and needs diagnostic filters before any destructive update is enabled.

Incorrect Answers

B:

Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. This approach instead addresses UI Policy onLoad and reverse behavior controls. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. The targeted response is: Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects. Scenario: A scheduled cleanup script queries the wrong table and needs diagnostic filters before any destructive update is enabled.

C:

Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. This approach instead addresses Business Rule recursion and idempotent side effects. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The targeted response is: Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects. Scenario: A scheduled cleanup script queries the wrong table and needs diagnostic filters before any destructive update is enabled.

D:

Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. This approach instead addresses Coalesce keys and update versus insert control. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. The targeted response is: Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects. Scenario: A scheduled cleanup script queries the wrong table and needs diagnostic filters before any destructive update is enabled.

Question 74

A transferred chat loses the user's issue summary and the live agent asks the customer to repeat private account information unnecessarily. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response.
  2. The correct trigger starts one flow execution and approved actions modify the intended records without unrelated updates.
  3. Each security obligation has a named accountable party, and customer-managed access is not incorrectly delegated to vendor hosting support.
  4. An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task.

Explanation

Correct Answer

D:

An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. A chat session ending without a supported answer is not a successfully completed service request; escalation must be observable. Scenario: A transferred chat loses the user's issue summary and the live agent asks the customer to repeat private account information unnecessarily.

Incorrect Answers

A:

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: An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. Scenario: A transferred chat loses the user's issue summary and the live agent asks the customer to repeat private account information unnecessarily.

B:

The correct trigger starts one flow execution and approved actions modify the intended records without unrelated updates. This result would support Workflow Studio trigger and action design, not the specific outcome required in the case. The relevant acceptance test is: An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. Scenario: A transferred chat loses the user's issue summary and the live agent asks the customer to repeat private account information unnecessarily.

C:

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: An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. Scenario: A transferred chat loses the user's issue summary and the live agent asks the customer to repeat private account information unnecessarily.

Question 75

A report over Task needs to include several extended task classes without assuming each class stores a copied master row. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. The desired behavior changes in the intended scope and unchanged applications continue operating with known property values.
  2. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  3. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  4. Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.
  5. Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table.

Explanation

Correct Answers

C:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. Table extension reuses parent schema and behavior; creating duplicate fields with similar labels can cause divergent security and data maintenance. The appropriate response is: Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. Scenario: A report over Task needs to include several extended task classes without assuming each class stores a copied master row.

E:

Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. Table extension reuses parent schema and behavior; creating duplicate fields with similar labels can cause divergent security and data maintenance. Verify prerequisites with: Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. Scenario: A report over Task needs to include several extended task classes without assuming each class stores a copied master row.

Incorrect Answers

A:

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: Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. Together with: Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. Scenario: A report over Task needs to include several extended task classes without assuming each class stores a copied master row.

B:

Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant 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: Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. Together with: Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. Scenario: A report over Task needs to include several extended task classes without assuming each class stores a copied master row.

D:

Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. This step may apply to Scheduled data imports and operational cleanup but is not one of the complementary requirements in this case. The intended pair is: Design a new ServiceNow table with the appropriate extension/inheritance strategy, recognizing inherited fields and access behavior instead of copying the entire Task schema into a parallel table. Together with: Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. Scenario: A report over Task needs to include several extended task classes without assuming each class stores a copied master row.

Question 76

A security team publishes an internal incident-response runbook into a knowledge base visible to external requesters. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process.
  2. A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values.
  3. The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible.
  4. Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies.

Explanation

Correct Answer

C:

The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible. Knowledge Management supports governed reusable answers; an article's existence or a public title is not proof it is published or readable by every user. Scenario: A security team publishes an internal incident-response runbook into a knowledge base visible to external requesters.

Incorrect Answers

A:

Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. This result would support Knowledge search feedback and content improvement, not the specific outcome required in the case. The relevant acceptance test is: The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible. Scenario: A security team publishes an internal incident-response runbook into a knowledge base visible to external requesters.

B:

A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values. This result would support Service Catalog item variables and validation, not the specific outcome required in the case. The relevant acceptance test is: The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible. Scenario: A security team publishes an internal incident-response runbook into a knowledge base visible to external requesters.

D:

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 target audience finds and opens the approved published article, while draft or restricted content remains inaccessible. Scenario: A security team publishes an internal incident-response runbook into a knowledge base visible to external requesters.

Question 77

A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
  2. Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility.
  3. A properly assigned task has an auditable state and owner, and the workflow records its changes rather than relying on emails as the authoritative queue.
  4. Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily.
  5. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.

Explanation

Correct Answers

A:

Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Changing a form section only changes presentation; a dictionary requirement or ACL still applies after fields are rearranged. The appropriate response is: Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Scenario: A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing.

D:

Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Changing a form section only changes presentation; a dictionary requirement or ACL still applies after fields are rearranged. Verify prerequisites with: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing.

Incorrect Answers

B:

Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility. This step may apply to Form Designer and field ordering by view but is not one of the complementary requirements in this case. The intended pair is: Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Together with: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing.

C:

A properly assigned task has an auditable state and owner, and the workflow records its changes rather than relying on emails as the authoritative queue. This step may apply to Platform task and service management capabilities but is not one of the complementary requirements in this case. The intended pair is: Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Together with: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing.

E:

Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration. This step may apply to Related lists and record relationships but is not one of the complementary requirements in this case. The intended pair is: Organize form fields into accessible sections and validate labels, tabs and dependencies for the intended user role without altering table schema unnecessarily. Together with: Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. Scenario: A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing.

Question 78

An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. 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.
  2. Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership.
  3. Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log.
  4. A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.
  5. Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb.

Explanation

Correct Answers

B:

Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. The appropriate response is: Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. Scenario: An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing.

E:

Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. Verify prerequisites with: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing.

Incorrect Answers

A:

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 step may apply to List tags and saved filter sharing but is not one of the complementary requirements in this case. The intended pair is: Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. Together with: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing.

C:

Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. This step may apply to Task approval and state workflow audit but is not one of the complementary requirements in this case. The intended pair is: Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. Together with: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing.

D:

A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data. This step may apply to Platform analytics as a reporting capability but is not one of the complementary requirements in this case. The intended pair is: Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. Together with: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: An agent adds Active is true to a complex OR filter and the count unexpectedly increases rather than narrowing.

Question 79

A password-reset article refers to an old identity provider and remains the top self-service search result. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. A user receives an authorized knowledge result or a confirmed catalog request number, and a failed submission is explicitly reported.
  2. A verified weakness is remediated or formally accepted, and the posture finding reflects the tested resulting state.
  3. Search results lead to the current approved article, and the superseded instructions no longer mislead requesters.
  4. Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process.

Explanation

Correct Answer

C:

Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. Reusing knowledge is valuable only if ownership, currency and intended audience are maintained; a search hit is not proof of current policy. Scenario: A password-reset article refers to an old identity provider and remains the top self-service search result.

Incorrect Answers

A:

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: Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. Scenario: A password-reset article refers to an old identity provider and remains the top self-service search result.

B:

A verified weakness is remediated or formally accepted, and the posture finding reflects the tested resulting state. This result would support Security Center security posture triage, not the specific outcome required in the case. The relevant acceptance test is: Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. Scenario: A password-reset article refers to an old identity provider and remains the top self-service search result.

D:

Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. This result would support Knowledge search feedback and content improvement, not the specific outcome required in the case. The relevant acceptance test is: Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. Scenario: A password-reset article refers to an old identity provider and remains the top self-service search result.

Question 80

Several engineers use one shared admin account and no one can identify who changed a high-impact ACL. Which configuration or administrative response BEST addresses the primary issue?

  1. Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights.
  2. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.
  3. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.
  4. Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally.

Explanation

Correct Answer

C:

Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. Verify prerequisites with: Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.

Incorrect Answers

A:

Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. This approach instead addresses Workflow Studio debugging and Run As privileges. Flow execution identity and action permissions affect outcomes; rerunning as an administrator may hide missing delegation rather than fix it. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.

B:

Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. This approach instead addresses Scoped application permissions and cross-scope access. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.

D:

Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. This approach instead addresses Tenant data handling and retention governance. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. The targeted response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: Several engineers use one shared admin account and no one can identify who changed a high-impact ACL.

ServiceNow Certified System Administrator (CSA) Practice Tests