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 28

Question 270

A self-service chat selects an ineligible catalog item and silently drops the request without explanation. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions.
  2. Inspect available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes.
  3. Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance.
  4. Inspect fallback event, live agent availability, chat routing, transcript scope, authorization, and resulting task record.

Explanation

Correct Answer

B:

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: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

Incorrect Answers

A:

Inspect catalog item visibility, variable type, variable set reuse, choice values, conditions, reference table, and test submissions. This evidence is relevant to Service Catalog item variables and validation, 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: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

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 available published topics, knowledge access, catalog item eligibility, fulfillment record identifiers and tool/flow outcomes. Scenario: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

D:

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: A self-service chat selects an ineligible catalog item and silently drops the request without explanation.

Question 271

A form collects issue information but no mapping sends those producer variables to the newly created case. 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. The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions.
  3. The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results.
  4. A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data.

Explanation

Correct Answer

D:

A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. Record producers can simplify creating records; ordering a catalog item often creates request artifacts such as RITMs and catalog tasks. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

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: A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

B:

The request advances only after required approvals and produces the correct assignee tasks with traceable state transitions. This result would support Catalog approval fulfillment and lifecycle, not the specific outcome required in the case. The relevant acceptance test is: A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

C:

The record references the intended target sys_id and shows a readable label without ambiguous or unauthorized results. This result would support Reference fields and display values in the data dictionary, not the specific outcome required in the case. The relevant acceptance test is: A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. Scenario: A form collects issue information but no mapping sends those producer variables to the newly created case.

Question 272

An API consumer tries to join assignment groups by their display name rather than by stable sys_id references. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  2. Inspect ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results.
  3. Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI.
  4. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.

Explanation

Correct Answer

D:

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: An API consumer tries to join assignment groups by their display name rather than by stable sys_id references.

Incorrect Answers

A:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This evidence is relevant to Table extension and inherited task fields, 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: An API consumer tries to join assignment groups by their display name rather than by stable sys_id references.

B:

Inspect ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results. This evidence is relevant to ACL debugging of roles conditions and scripts, 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: An API consumer tries to join assignment groups by their display name rather than by stable sys_id references.

C:

Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. This evidence is relevant to UI Policy versus server-side data enforcement, not the most diagnostic first check for this failure. Examine: Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. Scenario: An API consumer tries to join assignment groups by their display name rather than by stable sys_id references.

Question 273

A troubleshooting change appears ineffective until the team checks its correct scope and any relevant caching behavior. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution.
  2. Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance.
  3. Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history.
  4. Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior.

Explanation

Correct Answer

C:

Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. System properties can have broad platform effects; undocumented edits and guesswork are not a safe substitute for release-specific guidance. The appropriate response is: Change a documented ServiceNow system property or application setting only after confirming its scope, default, and impact on other modules, then test in a nonproduction environment. Scenario: A troubleshooting change appears ineffective until the team checks its correct scope and any relevant caching behavior.

Incorrect Answers

A:

Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. This evidence is relevant to Plugin feature validation after activation, not the most diagnostic first check for this failure. Examine: Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. Scenario: A troubleshooting change appears ineffective until the team checks its correct scope and any relevant caching behavior.

B:

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 property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. Scenario: A troubleshooting change appears ineffective until the team checks its correct scope and any relevant caching behavior.

D:

Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior. This evidence is relevant to Catalog approval fulfillment and lifecycle, not the most diagnostic first check for this failure. Examine: Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. Scenario: A troubleshooting change appears ineffective until the team checks its correct scope and any relevant caching behavior.

Question 274

A change manager adds a Risk field to the wrong form view and agents report no visible difference. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data.
  2. Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
  3. Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.
  4. Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes.

Explanation

Correct Answer

D:

Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. A form view controls field presentation; it cannot safely replace field-level ACL checks or enforce all server-side data requirements. The appropriate response is: Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility. Scenario: A change manager adds a Risk field to the wrong form view and agents report no visible difference.

Incorrect Answers

A:

Inspect CI class, identifiers, ownership, lifecycle state, relationships, and source/discovery data. This evidence is relevant to CMDB class hierarchy and CI record modeling, not the most diagnostic first check for this failure. Examine: Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. Scenario: A change manager adds a Risk field to the wrong form view and agents report no visible difference.

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: Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. Scenario: A change manager adds a Risk field to the wrong form view and agents report no visible difference.

C:

Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. This evidence is relevant to List versus form anatomy and record identity, not the most diagnostic first check for this failure. Examine: Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. Scenario: A change manager adds a Risk field to the wrong form view and agents report no visible difference.

Question 275

A record form has thirty fields under one tab and users regularly miss the assignment details needed for routing. 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 existing form sections, section order, effective form view, field presence and related UI policy behavior.
  3. Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes.
  4. Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation.

Explanation

Correct Answer

B:

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.

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 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:

Inspect table/view selection, field dictionary attributes, sections, personal overrides, and UI policies before publishing layout changes. This evidence is relevant to Form Designer and field ordering by view, not the most diagnostic first check for this failure. Examine: 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.

D:

Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation. This evidence is relevant to Flow approvals and wait-for-condition boundaries, not the most diagnostic first check for this failure. Examine: 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 276

An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  2. Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact.
  3. A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values.
  4. Inspect identification keys, data source, authoritative attributes, reconciliation precedence, IRE results and duplicate CIs.
  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

D:

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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

Incorrect Answers

A:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This step may apply to Table extension and inherited task fields 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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

B:

Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. 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: 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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

C:

A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values. 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 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: An administrator deletes all duplicate-looking CIs without testing whether their identifiers refer to separate virtual machines.

Question 277

A data migration creates several unapproved reference records because reference field mapping lacks target validation. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records.
  2. The user navigates from the authorized list to the intended form or workspace and changes the correct record with an audit trail.
  3. A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked.
  4. Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data.

Explanation

Correct Answer

A:

The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. External display strings do not necessarily identify reference records, and scripts can create side effects beyond a simple field map. Scenario: A data migration creates several unapproved reference records because reference field mapping lacks target validation.

Incorrect Answers

B:

The user navigates from the authorized list to the intended form or workspace and changes the correct record with an audit trail. This result would support Core platform lists versus forms and workspaces, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A data migration creates several unapproved reference records because reference field mapping lacks target validation.

C:

A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. This result would support ACL debugging of roles conditions and scripts, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A data migration creates several unapproved reference records because reference field mapping lacks target validation.

D:

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: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: A data migration creates several unapproved reference records because reference field mapping lacks target validation.

Question 278

A new custom asset identifier exceeds the length of a string column and data is silently truncated by an upstream integration. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The intended child table applies the approved override while parent and sibling task forms preserve their current behavior.
  2. The user opens the intended application and reaches correctly authorized records without confusing a module shortcut with a duplicate data store.
  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

D:

The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. Scenario: A new custom asset identifier exceeds the length of a string column and data is silently truncated by an upstream integration.

Incorrect Answers

A:

The intended child table applies the approved override while parent and sibling task forms preserve their current behavior. This result would support Dictionary overrides on extended tables, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A new custom asset identifier exceeds the length of a string column and data is silently truncated by an upstream integration.

B:

The user opens the intended application and reaches correctly authorized records without confusing a module shortcut with a duplicate data store. This result would support Now Platform shared records and configurable applications, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A new custom asset identifier exceeds the length of a string column and data is silently truncated by an upstream integration.

C:

The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. This result would support Table extension and inherited task fields, not the specific outcome required in the case. The relevant acceptance test is: The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change. Scenario: A new custom asset identifier exceeds the length of a string column and data is silently truncated by an upstream integration.

Question 279

A vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results.
  2. Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.
  3. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.
  4. Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.
  5. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.

Explanation

Correct Answers

C:

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

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 ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results. This step may apply to ACL debugging of roles conditions and scripts 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 vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

B:

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

E:

The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning. This step may apply to Configurable form and workspace layout changes but is not one of the complementary requirements in this case. The intended pair is: 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 vendor reimports asset records nightly but duplicate assets appear because no unique coalesce key is configured.

Question 280

A form shows a friendly label for a choice field but an import sends an unknown underlying choice value. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage.
  2. Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes.
  3. 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.
  4. Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
  5. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.

Explanation

Correct Answers

A:

Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. Verify prerequisites with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

B:

Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. The appropriate response is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

Incorrect Answers

C:

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. This step may apply to Reference fields and display values in the data dictionary but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

D:

Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This step may apply to Table extension and inherited task fields but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

E:

The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning. This step may apply to Configurable form and workspace layout changes but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.

ServiceNow Certified System Administrator (CSA) Practice Tests