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 36

Question 350

A high-priority incident fires an outbound integration twice because two rules emit the same event on state change. Which configuration or administrative response BEST addresses the primary issue?

  1. Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths.
  2. Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access.
  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 Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome.

Explanation

Correct Answer

C:

Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. Verify prerequisites with: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

Incorrect Answers

A:

Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths. This approach instead addresses Client script versus Business Rule and API persistence. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. The targeted response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

B:

Use supported asynchronous client-to-server calls such as GlideAjax and scoped Script Includes for required server data, validating inputs and authorization without relying on synchronous browser-side database access. This approach instead addresses Client server scripting with GlideAjax and scoped APIs. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. The targeted 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: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

D:

Configure Virtual Agent topics with appropriate intents, conversation variables, eligibility rules and validation so users reach the right self-service outcome. This approach instead addresses Virtual Agent topic routing and conversation state. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. The targeted response is: Prevent unintended recursive Business Rule updates and repeated external side effects by using correct conditions, execution timing and safe record-update patterns. Scenario: A high-priority incident fires an outbound integration twice because two rules emit the same event on state change.

Question 351

A requester says reset my password but Virtual Agent launches the lost-laptop topic because utterance mapping is wrong. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data.
  2. The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response.
  3. When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values.
  4. The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.

Explanation

Correct Answer

B:

The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. A conversational topic is more than a chatbot text snippet; published state, access and flow integration govern its behavior. Scenario: A requester says reset my password but Virtual Agent launches the lost-laptop topic because utterance mapping is wrong.

Incorrect Answers

A:

A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. This result would support Record producer versus catalog item selection, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: A requester says reset my password but Virtual Agent launches the lost-laptop topic because utterance mapping is wrong.

C:

When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This result would support UI Policy actions for conditional field behavior, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: A requester says reset my password but Virtual Agent launches the lost-laptop topic because utterance mapping is wrong.

D:

The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step. This result would support Workflow Studio debugging and Run As privileges, not the specific outcome required in the case. The relevant acceptance test is: The requester is routed to an appropriate active topic and receives correct follow-up prompts or an explicit unsupported-path response. Scenario: A requester says reset my password but Virtual Agent launches the lost-laptop topic because utterance mapping is wrong.

Question 352

A transform coalesces on a common department name and overwrites the first matching user account. Which configuration or administrative response BEST addresses the primary issue?

  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. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.
  3. Use ServiceNow access control diagnostics to identify the exact ACL evaluation blocking an authorized operation, preserving unrelated security checks.
  4. Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.

Explanation

Correct Answer

B:

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

Incorrect Answers

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. This approach instead addresses Knowledge search feedback and content improvement. Knowledge feedback guides the content lifecycle; voting an article Helpful does not update the underlying process or grant requester access. The targeted response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

C:

Use ServiceNow access control diagnostics to identify the exact ACL evaluation blocking an authorized operation, preserving unrelated security checks. This approach instead addresses ACL debugging of roles conditions and scripts. An ACL may require multiple matching elements to pass; a user possessing one listed role does not guarantee an ACL condition or script will pass. The targeted response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

D:

Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. This approach instead addresses Scheduled data imports and operational cleanup. Scheduled imports require data quality, monitoring and cleanup as well as a timer; large or overlapping batches can harm platform performance. The targeted response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: A transform coalesces on a common department name and overwrites the first matching user account.

Question 353

A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.
  2. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  3. Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls.
  4. Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification.
  5. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.

Explanation

Correct Answers

C:

Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Security dashboards organize findings and help prioritization; they do not replace system ACLs, authentication, or independent verification of a fix. Verify prerequisites with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant.

D:

Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Security dashboards organize findings and help prioritization; they do not replace system ACLs, authentication, or independent verification of a fix. The appropriate response is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Scenario: A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant.

Incorrect Answers

A:

The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step. This step may apply to Workflow Studio debugging and Run As privileges but is not one of the complementary requirements in this case. The intended pair is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant.

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: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant.

E:

Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. This step may apply to Security Center evidence and posture exception control but is not one of the complementary requirements in this case. The intended pair is: Use supported Security Center capabilities to review security posture findings, prioritize actionable configuration risk and assign remediation without assuming a dashboard itself enforces all controls. Together with: Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. Scenario: A security administrator enables a dashboard widget and claims it automatically prevents every unsafe role grant.

Question 354

An administrator attempts to patch the managed database operating system directly instead of using the supported vendor platform process. Which configuration or administrative response BEST addresses the primary issue?

  1. Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance.
  2. 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.
  3. Publish a knowledge article through its supported draft/review/publish workflow, assigning it to the right knowledge base and checking article/user criteria for the intended audience.
  4. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.

Explanation

Correct Answer

A:

Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. A hosted ServiceNow service does not absolve customers of properly configured roles, ACLs and data handling; platform hosting and customer configuration are different responsibilities. Verify prerequisites with: Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. Scenario: An administrator attempts to patch the managed database operating system directly instead of using the supported vendor platform process.

Incorrect Answers

B:

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. This approach instead addresses Dictionary attributes and field type integrity. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. The targeted response is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Scenario: An administrator attempts to patch the managed database operating system directly instead of using the supported vendor platform process.

C:

Publish a knowledge article through its supported draft/review/publish workflow, assigning it to the right knowledge base and checking article/user criteria for the intended audience. This approach instead addresses Knowledge base article publication and access. 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. The targeted response is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Scenario: An administrator attempts to patch the managed database operating system directly instead of using the supported vendor platform process.

D:

Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. This approach instead addresses Audit and accountability for privileged instance operations. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. The targeted response is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Scenario: An administrator attempts to patch the managed database operating system directly instead of using the supported vendor platform process.

Question 355

Several engineers use one shared admin account and no one can identify who changed a high-impact ACL. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.
  2. Use ServiceNow access control diagnostics to identify the exact ACL evaluation blocking an authorized operation, preserving unrelated security checks.
  3. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  4. The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records.
  5. Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.

Explanation

Correct Answers

A:

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.

C:

Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. The appropriate 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.

Incorrect Answers

B:

Use ServiceNow access control diagnostics to identify the exact ACL evaluation blocking an authorized operation, preserving unrelated security checks. 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: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Together 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.

D:

The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. This step may apply to List filter conditions and breadcrumb logic but is not one of the complementary requirements in this case. The intended pair is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Together 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.

E:

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: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Together 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.

Question 356

An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases.
  2. Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.
  3. Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification.
  4. Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation.

Explanation

Correct Answer

D:

Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Accepting a known exception is a governance decision, not evidence the security configuration meets the baseline. The appropriate response is: Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

Incorrect Answers

A:

Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. This evidence is relevant to Reusable subflows and defined input output contracts, not the most diagnostic first check for this failure. Examine: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

B:

Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. This evidence is relevant to Coalesce keys and update versus insert control, not the most diagnostic first check for this failure. Examine: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

C:

Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification. This evidence is relevant to Security Center security posture triage, not the most diagnostic first check for this failure. Examine: Inspect flagged control, data sensitivity, exception approval, compensating evidence, expiration date and scan re-evaluation. Scenario: An administrator suppresses a security finding after a third-party plugin requires a temporary relaxed setting, but leaves no expiry.

Question 357

A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.
  2. An application incident can be traced through correct service relationships to affected service offerings and stakeholders.
  3. The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently.
  4. Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions.

Explanation

Correct Answer

D:

Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. A CMDB health score is only as meaningful as the selected rules and data sources; dashboards alone do not repair faulty CI relationships. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

Incorrect Answers

A:

The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning. This result would support Configurable form and workspace layout changes, not the specific outcome required in the case. The relevant acceptance test is: Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

B:

An application incident can be traced through correct service relationships to affected service offerings and stakeholders. This result would support Common Service Data Model service relationships, not the specific outcome required in the case. The relevant acceptance test is: Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

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: Important CIs and their relationships pass the defined health checks, and identified defects have accountable remediation rather than hidden exceptions. Scenario: A CMDB class has many duplicate entries created by a migration, but the team proposes changing only the report visualization.

Question 358

An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects.
  2. Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces.
  3. Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions.
  4. Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields.
  5. Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership.

Explanation

Correct Answers

A:

Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Visual Task Boards can be collaborative displays; board/card configuration determines whether a move changes a task field or only planning metadata. The appropriate response is: Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Scenario: An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected.

D:

Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Visual Task Boards can be collaborative displays; board/card configuration determines whether a move changes a task field or only planning metadata. Verify prerequisites with: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected.

Incorrect Answers

B:

Only eligible records appear as selectable values and unauthorized values remain rejected when requests are submitted via other interfaces. This step may apply to Catalog item reference qualifier and eligibility but is not one of the complementary requirements in this case. The intended pair is: Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Together with: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected.

C:

Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. 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: Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Together with: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected.

E:

Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. This step may apply to List filter conditions and breadcrumb logic but is not one of the complementary requirements in this case. The intended pair is: Choose data-driven or freeform Visual Task Board behavior according to whether cards should reflect underlying task records and configured lane fields. Together with: Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. Scenario: An administrator configures state-driven lanes but the board uses a filter that excludes the incidents managers expected.

Question 359

Two UI Policies target the same field with conflicting read-only actions and staff see inconsistent edit behavior. Which configuration or administrative response BEST addresses the primary issue?

  1. Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form.
  2. Separate configuration capture from application data migration, review update set collisions, and keep manual data-loading tasks explicit rather than assuming a commit reproduces every record.
  3. Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths.
  4. Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view.

Explanation

Correct Answer

D:

Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view. UI Policies guide form behavior; form presentation alone does not enforce security or guarantee validation of integrations and imported data. Verify prerequisites with: Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. Scenario: Two UI Policies target the same field with conflicting read-only actions and staff see inconsistent edit behavior.

Incorrect Answers

A:

Configure matching table and field ACLs for the requested operation and verify all conditions, scripts and roles with impersonation or diagnostic tools rather than hiding fields in a form. This approach instead addresses Table-level versus field-level access controls. For protected records, appropriate table-level and field-level ACL checks both matter; form visibility is not server-side authorization. The targeted response is: Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view. Scenario: Two UI Policies target the same field with conflicting read-only actions and staff see inconsistent edit behavior.

B:

Separate configuration capture from application data migration, review update set collisions, and keep manual data-loading tasks explicit rather than assuming a commit reproduces every record. This approach instead addresses Update set exclusions and collision resolution. System update sets are not a general backup or complete data-migration mechanism; preview and conflict management protect target instances. The targeted response is: Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view. Scenario: Two UI Policies target the same field with conflicting read-only actions and staff see inconsistent edit behavior.

C:

Put presentation-specific behavior in supported client mechanisms and durable record mutation or validation at the server layer, ensuring consistent behavior across UI and API paths. This approach instead addresses Client script versus Business Rule and API persistence. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. The targeted response is: Use UI Policy conditions and actions for supported client-side field visibility, mandatory and read-only behavior, and test reverse-if-false results under the correct view. Scenario: Two UI Policies target the same field with conflicting read-only actions and staff see inconsistent edit behavior.

Question 360

An onBefore transform script inadvertently ignores every row with a blank optional phone field. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person.
  2. The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records.
  3. The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change.
  4. Each CI has a consistent class and attributable relationships that support intended impact analysis.

Explanation

Correct Answer

B:

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: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

Incorrect Answers

A:

The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person. This result would support Task assignment group versus individual responsibility, 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: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

C:

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 imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

D:

Each CI has a consistent class and attributable relationships that support intended impact analysis. This result would support CMDB class hierarchy and CI record modeling, not the specific outcome required in the case. The relevant acceptance test is: The imported record references the correct existing target and malformed mappings fail visibly without writing orphaned or unexpected linked records. Scenario: An onBefore transform script inadvertently ignores every row with a blank optional phone field.

ServiceNow Certified System Administrator (CSA) Practice Tests