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 38

Question 370

A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership.
  2. Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
  3. Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record.
  4. Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration.

Explanation

Correct Answer

A:

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: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

Incorrect Answers

B:

Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. This evidence is relevant to Form sections and related layout configuration, not the most diagnostic first check for this failure. Examine: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

C:

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: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

D:

Inspect parent sys_id, child reference fields, relationship definition, user ACLs, and view configuration. This evidence is relevant to Related lists and record relationships, not the most diagnostic first check for this failure. Examine: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

Question 371

A vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns.
  2. Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows.
  3. Review order guide rules, included items, requested item quantities, variable mappings, eligibility conditions and downstream task generation.
  4. Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.

Explanation

Correct Answer

D:

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 vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

Incorrect Answers

A:

Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. This evidence is relevant to Scheduled data imports and operational cleanup, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

B:

Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. This evidence is relevant to Import reference resolution and transformation scripting, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

C:

Review order guide rules, included items, requested item quantities, variable mappings, eligibility conditions and downstream task generation. This evidence is relevant to Service Catalog order guide and request structure, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: A vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

Question 372

A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions.
  2. Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable.
  3. The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see.
  4. Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle.
  5. Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions.

Explanation

Correct Answers

A:

Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. The appropriate response is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Scenario: A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages.

D:

Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. Verify prerequisites with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages.

Incorrect Answers

B:

Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. This step may apply to Catalog approval fulfillment and lifecycle but is not one of the complementary requirements in this case. The intended pair is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages.

C:

The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. This step may apply to Next Experience application navigation and favorites but is not one of the complementary requirements in this case. The intended pair is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages.

E:

Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. This step may apply to Knowledge article review, validity and version lifecycle but is not one of the complementary requirements in this case. The intended pair is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Together with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A support portal form should create a new incident directly but an administrator models it as a hardware order with unnecessary fulfillment stages.

Question 373

After a form designer publishes a shared view, one user reports an older column order because they have a personal layout preference. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user.
  2. Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history.
  3. Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change.
  4. Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies.

Explanation

Correct Answer

A:

Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The appropriate response is: Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. Scenario: After a form designer publishes a shared view, one user reports an older column order because they have a personal layout preference.

Incorrect Answers

B:

Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. This evidence is relevant to Instance properties and scoped configuration control, not the most diagnostic first check for this failure. Examine: Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Scenario: After a form designer publishes a shared view, one user reports an older column order because they have a personal layout preference.

C:

Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. This evidence is relevant to UI Policy onLoad and reverse behavior controls, not the most diagnostic first check for this failure. Examine: Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Scenario: After a form designer publishes a shared view, one user reports an older column order because they have a personal layout preference.

D:

Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. This evidence is relevant to Instance branding and portal experience settings, not the most diagnostic first check for this failure. Examine: Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. Scenario: After a form designer publishes a shared view, one user reports an older column order because they have a personal layout preference.

Question 374

An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it. 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. Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result.
  3. A configuration is validated in its designated test environment and deployed to production without an unapproved change on live records.
  4. Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions.
  5. Review search terms, article categories, user access, helpfulness feedback, version, broken links and resolution context.

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: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

E:

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: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

Incorrect Answers

B:

Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. This step may apply to Knowledge article review, validity and version lifecycle 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: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

C:

A configuration is validated in its designated test environment and deployed to production without an unapproved change on live records. This step may apply to Instance lifecycle and environment separation 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: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

D:

Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions. This step may apply to Service Catalog item variables and validation 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: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

Question 375

The health dashboard reports completeness while hundreds of application services lack required upstream dependency relationships. 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. 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.
  3. 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.
  4. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.

Explanation

Correct Answer

B:

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: The health dashboard reports completeness while hundreds of application services lack required upstream dependency relationships.

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: 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: The health dashboard reports completeness while hundreds of application services lack required upstream dependency relationships.

C:

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: 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: The health dashboard reports completeness while hundreds of application services lack required upstream dependency relationships.

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: 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: The health dashboard reports completeness while hundreds of application services lack required upstream dependency relationships.

Question 376

A team requests a production rollout based only on the presence of a newly installed module. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies.
  2. Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution.
  3. Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance.
  4. Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view.

Explanation

Correct Answer

B:

Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. The appropriate response is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Scenario: A team requests a production rollout based only on the presence of a newly installed module.

Incorrect Answers

A:

Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. This evidence is relevant to Instance branding and portal experience settings, not the most diagnostic first check for this failure. Examine: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A team requests a production rollout based only on the presence of a newly installed module.

C:

Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance. This evidence is relevant to Application installation and plugin activation preflight, not the most diagnostic first check for this failure. Examine: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A team requests a production rollout based only on the presence of a newly installed module.

D:

Review action visibility, UI policy ordering, client scripts, field state, and save conditions for the affected view. This evidence is relevant to Advanced form configuration and conditional display, not the most diagnostic first check for this failure. Examine: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A team requests a production rollout based only on the presence of a newly installed module.

Question 377

An editor creates a second form section with the same label and a support agent cannot locate the original approval field. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls.
  2. A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result.
  3. The intended users see the approved form field order while role-based access and record data remain intact.
  4. The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change.

Explanation

Correct Answer

A:

Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. Changing a form section only changes presentation; a dictionary requirement or ACL still applies after fields are rearranged. Scenario: An editor creates a second form section with the same label and a support agent cannot locate the original approval field.

Incorrect Answers

B:

A new record receives the intended reusable defaults, remains editable under policy, and saves with an auditable result. This result would support Form templates and controlled record creation, not the specific outcome required in the case. The relevant acceptance test is: Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. Scenario: An editor creates a second form section with the same label and a support agent cannot locate the original approval field.

C:

The intended users see the approved form field order while role-based access and record data remain intact. This result would support Form Designer and field ordering by view, not the specific outcome required in the case. The relevant acceptance test is: Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. Scenario: An editor creates a second form section with the same label and a support agent cannot locate the original approval field.

D:

The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. This result would support Dictionary attributes and field type integrity, not the specific outcome required in the case. The relevant acceptance test is: Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. Scenario: An editor creates a second form section with the same label and a support agent cannot locate the original approval field.

Question 378

An administrator finds sys_class_name on a child record and mistakes the parent record for a separate duplicate ticket. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. A verified weakness is remediated or formally accepted, and the posture finding reflects the tested resulting state.
  2. The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible.
  3. The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently.
  4. The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change.

Explanation

Correct Answer

C:

The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. Table extension reuses parent schema and behavior; creating duplicate fields with similar labels can cause divergent security and data maintenance. Scenario: An administrator finds sys_class_name on a child record and mistakes the parent record for a separate duplicate ticket.

Incorrect Answers

A:

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: The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. Scenario: An administrator finds sys_class_name on a child record and mistakes the parent record for a separate duplicate ticket.

B:

The target audience finds and opens the approved published article, while draft or restricted content remains inaccessible. This result would support Knowledge base article publication and access, not the specific outcome required in the case. The relevant acceptance test is: The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. Scenario: An administrator finds sys_class_name on a child record and mistakes the parent record for a separate duplicate ticket.

D:

The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. This result would support Dictionary attributes and field type integrity, not the specific outcome required in the case. The relevant acceptance test is: The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. Scenario: An administrator finds sys_class_name on a child record and mistakes the parent record for a separate duplicate ticket.

Question 379

A form collects issue information but no mapping sends those producer variables to the newly created case. Which configuration or administrative response BEST addresses the primary issue?

  1. Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle.
  2. Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete.
  3. Design catalog item questions with supported variable types, help text and mandatory settings so requesters supply the minimum information needed for fulfillment.
  4. Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger.

Explanation

Correct Answer

A:

Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. Verify prerequisites with: Inspect target record table, requested item process, producer variable mapping, requester expectations and catalog permissions. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

Incorrect Answers

B:

Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. This approach instead addresses Plugin feature validation after activation. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. The targeted response is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

C:

Design catalog item questions with supported variable types, help text and mandatory settings so requesters supply the minimum information needed for fulfillment. This approach instead addresses Service Catalog item variables and validation. Catalog variables collect request-specific input; a variable is not automatically a permanent column on the user or incident table. The targeted response is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

D:

Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. This approach instead addresses Reusable subflows and defined input output contracts. 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. The targeted response is: Choose a record producer when self-service should create a specific application record and a standard catalog item for a fulfillment request with requested-item lifecycle. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

Question 380

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

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

Explanation

Correct Answers

A:

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

C:

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

Incorrect Answers

B:

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

D:

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

E:

Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. This step may apply to CMDB health completeness correctness and relationship audits but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.

ServiceNow Certified System Administrator (CSA) Practice Tests