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 32

Question 310

A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets. Which configuration or administrative response BEST addresses the primary issue?

  1. Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths.
  2. Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility.
  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. Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb.

Explanation

Correct Answer

D:

Build a ServiceNow list filter with explicitly grouped AND/OR conditions, test representative records, and save it at the correct visibility rather than relying on a misleading breadcrumb. AND/OR grouping changes a list filter's meaning; a visual breadcrumb is not a proof the predicate selects the right records. Verify prerequisites with: Review field names, encoded filter conditions, operator precedence, expected matching records, user roles, and filter ownership. Scenario: A team wants incidents opened this week with State not Closed, but an ungrouped OR condition includes old closed tickets.

Incorrect Answers

A:

Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. This approach instead addresses UI Policy onLoad and reverse behavior controls. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. The targeted response is: 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.

B:

Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility. This approach instead addresses Form Designer and field ordering by view. A form view controls field presentation; it cannot safely replace field-level ACL checks or enforce all server-side data requirements. The targeted 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.

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

Question 311

A support analyst closes an incident while an associated approval remains pending, despite a required gate. Which configuration or administrative response BEST addresses the primary issue?

  1. Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility.
  2. 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.
  3. Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation.
  4. Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions.

Explanation

Correct Answer

D:

Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. Task states, approval records and email notifications have distinct meanings; an email sent does not mean approval granted. Verify prerequisites with: Inspect approval record state, referenced task, approver account, notifications, business rule/flow outcomes, and audit log. Scenario: A support analyst closes an incident while an associated approval remains pending, despite a required gate.

Incorrect Answers

A:

Use the correct form layout or Form Designer for the target table and view, preserving mandatory fields and checking workspace compatibility. This approach instead addresses Form Designer and field ordering by view. A form view controls field presentation; it cannot safely replace field-level ACL checks or enforce all server-side data requirements. The targeted response is: Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. Scenario: A support analyst closes an incident while an associated approval remains pending, despite a required gate.

B:

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 task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. Scenario: A support analyst closes an incident while an associated approval remains pending, despite a required gate.

C:

Coordinate conditional form display behavior, UI actions, and form configuration against the correct table/view so users are guided without bypassing server-side validation. This approach instead addresses Advanced form configuration and conditional display. Conditional presentation helps users but does not alone enforce security or data integrity for imports and APIs. The targeted response is: Use task-related approvals and state transitions with explicit approver identity and audit history instead of treating notifications as completed business decisions. Scenario: A support analyst closes an incident while an associated approval remains pending, despite a required gate.

Question 312

A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation.
  2. Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation.
  3. Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result.
  4. Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions.
  5. Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data.

Explanation

Correct Answers

C:

Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Reusing knowledge is valuable only if ownership, currency and intended audience are maintained; a search hit is not proof of current policy. Verify prerequisites with: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

D:

Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Reusing knowledge is valuable only if ownership, currency and intended audience are maintained; a search hit is not proof of current policy. The appropriate response is: Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

Incorrect Answers

A:

The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. This step may apply to Trend indicators versus transactional reports but is not one of the complementary requirements in this case. The intended pair is: Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Together with: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

B:

Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation. This step may apply to Flow approvals and wait-for-condition boundaries but is not one of the complementary requirements in this case. The intended pair is: Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Together with: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

E:

Provide an explicit Virtual Agent escalation to an available human support channel when automation cannot resolve a case, preserving context without exposing unrelated private transcript data. This step may apply to Virtual Agent human handoff and fallback but is not one of the complementary requirements in this case. The intended pair is: Manage review dates and revised versions of knowledge articles, retiring outdated procedures while keeping a traceable approval history and current search result. Together with: Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. Scenario: A knowledge manager edits a published runbook without reviewing whether the workflow requires a new version or approval.

Question 313

A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change.
  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. Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths.
  4. Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies.
  5. Inspect table name, field conditions, row limits, running identity, authorization checks, result count, and transaction logs.

Explanation

Correct Answers

A:

Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. The appropriate response is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

C:

Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. A UI Policy can behave differently on initial load and later changes; ignoring reverse conditions often leaves stale field states. Verify prerequisites with: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

Incorrect Answers

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 step may apply to Update set exclusions and collision resolution but is not one of the complementary requirements in this case. The intended pair is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Together with: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

D:

Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies. This step may apply to Tenant data handling and retention governance but is not one of the complementary requirements in this case. The intended pair is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Together with: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

E:

Inspect table name, field conditions, row limits, running identity, authorization checks, result count, and transaction logs. This step may apply to GlideRecord server-side query and secure result handling but is not one of the complementary requirements in this case. The intended pair is: Configure whether conditional UI Policy behavior applies when a form loads and whether actions reverse when its condition becomes false; verify all transition paths. Together with: Inspect policy On load and Reverse if false settings, current form values, action list, and event sequence when fields change. Scenario: A catalog-related form opens on an already closed task but a conditional UI Policy never applies until the user touches a field.

Question 314

A user sees a read-only field in one view and concludes the entire table has no write ACL. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect UI type, selected view or workspace page, field/component mapping, current actions, layout inheritance and role-based visibility.
  2. Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records.
  3. Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts.
  4. Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance.

Explanation

Correct Answer

B:

Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. A list aggregates records, a form edits a selected record, and a workspace can wrap multiple components; these are interfaces over records, not independent data copies. The appropriate response is: Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. Scenario: A user sees a read-only field in one view and concludes the entire table has no write ACL.

Incorrect Answers

A:

Inspect UI type, selected view or workspace page, field/component mapping, current actions, layout inheritance and role-based visibility. This evidence is relevant to Configurable form and workspace layout changes, not the most diagnostic first check for this failure. Examine: Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. Scenario: A user sees a read-only field in one view and concludes the entire table has no write ACL.

C:

Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. This evidence is relevant to UI Policy actions for conditional field behavior, not the most diagnostic first check for this failure. Examine: Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. Scenario: A user sees a read-only field in one view and concludes the entire table has no write ACL.

D:

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: Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. Scenario: A user sees a read-only field in one view and concludes the entire table has no write ACL.

Question 315

A catalog form collects passport numbers even though only a non-sensitive employee identifier is needed for fulfillment. Which configuration or administrative response BEST addresses the primary issue?

  1. Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations.
  2. Resolve imported reference values and apply documented transform scripts only when ordinary field mapping is insufficient, with safe handling of absent targets.
  3. 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.
  4. Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally.

Explanation

Correct Answer

D:

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 catalog form collects passport numbers even though only a non-sensitive employee identifier is needed for fulfillment.

Incorrect Answers

A:

Use approved elevated-role workflows and audit security-related configuration changes instead of leaving permanent broad privileges active for routine operations. This approach instead addresses Elevated security administration and role boundaries. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. The targeted 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 catalog form collects passport numbers even though only a non-sensitive employee identifier is needed for fulfillment.

B:

Resolve imported reference values and apply documented transform scripts only when ordinary field mapping is insufficient, with safe handling of absent targets. This approach instead addresses Import reference resolution and transformation scripting. External display strings do not necessarily identify reference records, and scripts can create side effects beyond a simple field map. The targeted 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 catalog form collects passport numbers even though only a non-sensitive employee identifier is needed for fulfillment.

C:

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. This approach instead addresses Instance properties and scoped configuration control. System properties can have broad platform effects; undocumented edits and guesswork are not a safe substitute for release-specific guidance. The targeted 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 catalog form collects passport numbers even though only a non-sensitive employee identifier is needed for fulfillment.

Question 316

A form hides a Reason field when Urgency is Low but never restores it when the user changes Urgency to High. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect request, requested item, catalog task, approver records, routing conditions, flow history, and terminal state behavior.
  2. Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts.
  3. Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval.
  4. Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI.

Explanation

Correct Answer

B:

Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. UI Policies guide form behavior; form presentation alone does not enforce security or guarantee validation of integrations and imported data. The appropriate 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: A form hides a Reason field when Urgency is Low but never restores it when the user changes Urgency to High.

Incorrect Answers

A:

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 affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. Scenario: A form hides a Reason field when Urgency is Low but never restores it when the user changes Urgency to High.

C:

Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval. This evidence is relevant to Update set creation completion and ordered promotion, not the most diagnostic first check for this failure. Examine: Inspect affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. Scenario: A form hides a Reason field when Urgency is Low but never restores it when the user changes Urgency to High.

D:

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 affected table, condition, UI policy order, action properties, form load behavior, and conflicting client scripts. Scenario: A form hides a Reason field when Urgency is Low but never restores it when the user changes Urgency to High.

Question 317

An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights.
  2. Inspect trigger table and changes, execution context, action configuration, input mappings, flow activation state, and run history.
  3. The intended child table applies the approved override while parent and sibling task forms preserve their current behavior.
  4. Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior.
  5. Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering.

Explanation

Correct Answers

D:

Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Reference qualifiers filter choices for usability and data correctness but do not grant or replace table ACLs. The appropriate response is: Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

E:

Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Reference qualifiers filter choices for usability and data correctness but do not grant or replace table ACLs. Verify prerequisites with: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

Incorrect Answers

A:

Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. 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: Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Together with: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

B:

Inspect trigger table and changes, execution context, action configuration, input mappings, flow activation state, and run history. This step may apply to Workflow Studio trigger and action design but is not one of the complementary requirements in this case. The intended pair is: Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Together with: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

C:

The intended child table applies the approved override while parent and sibling task forms preserve their current behavior. This step may apply to Dictionary overrides on extended tables but is not one of the complementary requirements in this case. The intended pair is: Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering. Together with: Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. Scenario: An API submits a sys_id not shown in the user-facing reference list, and the team assumes the UI qualifier alone is a security barrier.

Question 318

An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows.
  2. Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities.
  3. A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked.
  4. UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors.

Explanation

Correct Answer

B:

Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities. Some sensitive security edits require elevated authority; granting broad persistent admin privileges is not a substitute for deliberate authorization. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Incorrect Answers

A:

The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. This result would support Scheduled data imports and operational cleanup, not the specific outcome required in the case. The relevant acceptance test is: Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

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: Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

D:

UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. This result would support Client script versus Business Rule and API persistence, not the specific outcome required in the case. The relevant acceptance test is: Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities. Scenario: An administrator can edit ordinary incident forms but cannot modify a security rule without the necessary elevated role.

Question 319

A custom Facilities task table needs Assignment group and State like Task but the developer proposes recreating these fields manually. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Imported records land on the intended table with expected field values and failed source rows are reported without corrupting existing data.
  2. The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently.
  3. The designated user performs only approved duties, and a nonmember account cannot access the restricted management action.
  4. The target instance receives intended configurations, target-specific data loads occur through approved channels, and no unrelated customization is overwritten.

Explanation

Correct Answer

B:

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: A custom Facilities task table needs Assignment group and State like Task but the developer proposes recreating these fields manually.

Incorrect Answers

A:

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 child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. Scenario: A custom Facilities task table needs Assignment group and State like Task but the developer proposes recreating these fields manually.

C:

The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. This result would support User group and role assignment principle of least privilege, 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: A custom Facilities task table needs Assignment group and State like Task but the developer proposes recreating these fields manually.

D:

The target instance receives intended configurations, target-specific data loads occur through approved channels, and no unrelated customization is overwritten. This result would support Update set exclusions and collision resolution, 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: A custom Facilities task table needs Assignment group and State like Task but the developer proposes recreating these fields manually.

Question 320

A manager publishes a personal filter but other team members cannot find it in their filter choices. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies.
  2. Authorized colleagues see a shared organizational filter while personal tags and ACL-protected records remain properly scoped.
  3. The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records.
  4. The record form shows only legitimately related child records, with unchanged link integrity when a child is edited.

Explanation

Correct Answer

B:

Authorized colleagues see a shared organizational filter while personal tags and ACL-protected records remain properly scoped. Tags organize records and filters select records; neither overrides read permissions nor creates task assignment automatically. Scenario: A manager publishes a personal filter but other team members cannot find it in their filter choices.

Incorrect Answers

A:

Sensitive records are accessible only to approved roles and retained or disposed according to documented customer policies. This result would support Tenant data handling and retention governance, not the specific outcome required in the case. The relevant acceptance test is: Authorized colleagues see a shared organizational filter while personal tags and ACL-protected records remain properly scoped. Scenario: A manager publishes a personal filter but other team members cannot find it in their filter choices.

C:

The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records. This result would support List filter conditions and breadcrumb logic, not the specific outcome required in the case. The relevant acceptance test is: Authorized colleagues see a shared organizational filter while personal tags and ACL-protected records remain properly scoped. Scenario: A manager publishes a personal filter but other team members cannot find it in their filter choices.

D:

The record form shows only legitimately related child records, with unchanged link integrity when a child is edited. This result would support Related lists and record relationships, not the specific outcome required in the case. The relevant acceptance test is: Authorized colleagues see a shared organizational filter while personal tags and ACL-protected records remain properly scoped. Scenario: A manager publishes a personal filter but other team members cannot find it in their filter choices.

ServiceNow Certified System Administrator (CSA) Practice Tests