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 88

Question 870

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 configuration or administrative response BEST addresses the primary issue?

  1. Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable.
  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. Design catalog item questions with supported variable types, help text and mandatory settings so requesters supply the minimum information needed for fulfillment.
  4. Restrict catalog variable references and item eligibility using supported qualifiers and user criteria while enforcing access independently of UI filtering.

Explanation

Correct Answer

D:

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:

Model fulfillment with appropriate catalog approval stages, requested-item ownership, and downstream catalog tasks so the request lifecycle is auditable and recoverable. This approach instead addresses Catalog approval fulfillment and lifecycle. REQ, RITM and catalog task are distinct records with different scopes; notifying a manager does not imply a requested item was approved. The targeted 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.

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

C:

Design catalog item questions with supported variable types, help text and mandatory settings so requesters supply the minimum information needed for fulfillment. This approach instead addresses Service Catalog item variables and validation. Catalog variables collect request-specific input; a variable is not automatically a permanent column on the user or incident table. The targeted response is: 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.

Question 871

A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form.
  2. Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape.
  3. The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see.
  4. Choose Business Rule timing (before, after, async, display) appropriate to the operation and validate event conditions and effects without treating a client script as database enforcement.
  5. 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.

Explanation

Correct Answers

A:

Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. The appropriate response is: 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. Scenario: A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data.

E:

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. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. Verify prerequisites with: Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. Scenario: A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data.

Incorrect Answers

B:

Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. This step may apply to Client server scripting with GlideAjax and scoped APIs but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. Scenario: A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data.

C:

The authorized user can consistently reach the intended module and saved favorite without changing which modules colleagues may see. This step may apply to Next Experience application navigation and favorites but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. Scenario: A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data.

D:

Choose Business Rule timing (before, after, async, display) appropriate to the operation and validate event conditions and effects without treating a client script as database enforcement. This step may apply to Business Rule timing and before after async display behavior but is not one of the complementary requirements in this case. The intended pair is: 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. Together with: Inspect client script type, Business Rule timing, read/write ACLs, scripted API behavior, and test records created outside the form. Scenario: A record is saved through a REST integration and the onChange client logic never executes, leaving inconsistent data.

Question 872

A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows.
  2. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.
  3. Represent configuration items in appropriate CMDB classes and validate core attributes and relationships rather than using generic text records for every device and service.
  4. Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs.
  5. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.

Explanation

Correct Answers

B:

Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. Verify prerequisites with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

D:

Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The appropriate response is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

Incorrect Answers

A:

Inspect reference lookup fields, valid sys_ids, onBefore/onAfter transform scripts, source payloads, transform errors and skipped rows. This step may apply to Import reference resolution and transformation scripting but is not one of the complementary requirements in this case. The intended pair is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

C:

Represent configuration items in appropriate CMDB classes and validate core attributes and relationships rather than using generic text records for every device and service. This step may apply to CMDB class hierarchy and CI record modeling but is not one of the complementary requirements in this case. The intended pair is: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

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: Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. Together with: Inspect current application scope, target resource, accessible-from policy, cross-scope privileges, calling user and effective ACLs. Scenario: A developer enables broad cross-scope privileges to fix one table read but inadvertently expands access to unrelated resources.

Question 873

An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.
  2. Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process.
  3. Search results lead to the current approved article, and the superseded instructions no longer mislead requesters.
  4. The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details.

Explanation

Correct Answer

B:

Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. Knowledge feedback guides the content lifecycle; voting an article Helpful does not update the underlying process or grant requester access. Scenario: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

Incorrect Answers

A:

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: Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. Scenario: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

C:

Search results lead to the current approved article, and the superseded instructions no longer mislead requesters. This result would support Knowledge article review, validity and version lifecycle, not the specific outcome required in the case. The relevant acceptance test is: Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. Scenario: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

D:

The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. This result would support Notification trigger recipient and content configuration, not the specific outcome required in the case. The relevant acceptance test is: Users locate the right approved information for representative queries and unresolved gaps enter a documented content maintenance process. Scenario: An article receives negative feedback due to missing screenshots and staff assume reassigning all incidents will fix it.

Question 874

A newly trained operator cannot tell whether the highlighted row in a list is the record open in the adjacent workspace pane. Which configuration or administrative response BEST addresses the primary issue?

  1. Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout.
  2. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  3. Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience.
  4. Select the supported form or workspace configuration tool for the desired interface and preview the outcome in a scoped test context before promoting it.

Explanation

Correct Answer

C:

Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. 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. Verify prerequisites with: Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. Scenario: A newly trained operator cannot tell whether the highlighted row in a list is the record open in the adjacent workspace pane.

Incorrect Answers

A:

Build a dashboard from correctly scoped reports or visualizations and validate viewer access to underlying data and dashboard sharing before rollout. This approach instead addresses Dashboards and Platform Analytics audience permissions. Sharing a dashboard is not a substitute for table ACLs; chart accuracy depends on data definitions and refresh timing. The targeted 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 newly trained operator cannot tell whether the highlighted row in a list is the record open in the adjacent workspace pane.

B:

Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. This approach instead addresses Per-user list and form personalization. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The targeted 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 newly trained operator cannot tell whether the highlighted row in a list is the record open in the adjacent workspace pane.

D:

Select the supported form or workspace configuration tool for the desired interface and preview the outcome in a scoped test context before promoting it. This approach instead addresses Configurable form and workspace layout changes. Traditional form layout tools and modern workspace configuration can target different surfaces; presentation changes do not replace table security. The targeted 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 newly trained operator cannot tell whether the highlighted row in a list is the record open in the adjacent workspace pane.

Question 875

A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history.
  2. Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user.
  3. Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies.
  4. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.

Explanation

Correct Answer

A:

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 support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

Incorrect Answers

B:

Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user. This evidence is relevant to Per-user list and form personalization, 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 support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

C:

Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. This evidence is relevant to Instance branding and portal experience settings, not the most diagnostic first check for this failure. Examine: Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. Scenario: A support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

D:

Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. This evidence is relevant to Reference fields and display values in the data dictionary, 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 support engineer copies a system property name from an old blog and plans to enable it without verifying the current release.

Question 876

An administrator proposes converting a populated string column to a reference field without evaluating existing records and integrations. Which configuration or administrative response BEST addresses the primary issue?

  1. Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type.
  2. Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record.
  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. 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.

Explanation

Correct Answer

D:

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: An administrator proposes converting a populated string column to a reference field without evaluating existing records and integrations.

Incorrect Answers

A:

Use a documented dictionary override when an inherited field requires a supported per-child behavior, without modifying the base Task definition for every other task type. This approach instead addresses Dictionary overrides on extended tables. An inherited field may have per-table overrides; editing the parent entry can affect every child table unexpectedly. The targeted 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: An administrator proposes converting a populated string column to a reference field without evaluating existing records and integrations.

B:

Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. This approach instead addresses Platform task and service management capabilities. The platform coordinates records and workflow actions; a notification, dashboard, or module link is not a substitute for task state and ownership. The targeted 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: An administrator proposes converting a populated string column to a reference field without evaluating existing records and integrations.

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 approach instead addresses Reference fields and display values in the data dictionary. A ServiceNow reference is stored as a record identifier, while users commonly see the referenced record's display value. The targeted 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: An administrator proposes converting a populated string column to a reference field without evaluating existing records and integrations.

Question 877

A notification template includes a sensitive field that should not appear in messages sent to external requesters. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied.
  2. The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details.
  3. One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue.
  4. The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation.

Explanation

Correct Answer

B:

The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. A notification requires a matching trigger and recipient as well as a delivery path; saving its record does not itself send email. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

Incorrect Answers

A:

Only the approved cross-scope action succeeds, with unauthorized callers and unrelated tables denied. This result would support Scoped application permissions and cross-scope access, not the specific outcome required in the case. The relevant acceptance test is: The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

C:

One qualifying event produces the intended message and failures are attributable to a specific trigger, recipient or outbound delivery issue. This result would support Event-driven messaging and notification diagnostics, not the specific outcome required in the case. The relevant acceptance test is: The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

D:

The reported trend reproduces from recorded observations across comparable periods and aligns with its documented calculation. This result would support Trend indicators versus transactional reports, not the specific outcome required in the case. The relevant acceptance test is: The correct recipient receives a relevant notification exactly when the governed condition occurs and does not receive restricted details. Scenario: A notification template includes a sensitive field that should not appear in messages sent to external requesters.

Question 878

A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list. Which configuration or administrative response BEST addresses the primary issue?

  1. Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record.
  2. Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference.
  3. 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.
  4. Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts.

Explanation

Correct Answer

D:

Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts. Analytics provides views of governed source data, not a replacement for the underlying record lifecycle or ACL model. Verify prerequisites with: Check data source, table ACLs, report condition, aggregation, refresh timing, and roles allowed to view the visualization. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

Incorrect Answers

A:

Choose the relevant ServiceNow task-oriented application and supported workflow capabilities for tracking owned work, rather than assuming a dashboard or email message is itself a durable process record. This approach instead addresses Platform task and service management capabilities. The platform coordinates records and workflow actions; a notification, dashboard, or module link is not a substitute for task state and ownership. The targeted response is: Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

B:

Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference. This approach instead addresses Next Experience application navigation and favorites. An All menu module is a navigation target, while Favorites is a personal shortcut; absence of a module may instead reflect roles or installed application state. The targeted response is: Use supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

C:

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 supported report and dashboard capabilities against authorized table records, with definitions and audience permissions, rather than relying on a screenshot of changing record counts. Scenario: A supervisor creates a chart of active incidents but the count is inconsistent with the same team's filtered list.

Question 879

A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application. Which configuration or administrative response BEST addresses the primary issue?

  1. Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals.
  2. Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production.
  3. Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule.
  4. Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance.

Explanation

Correct Answer

D:

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: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.

Incorrect Answers

A:

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: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.

B:

Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. This approach instead addresses Coalesce keys and update versus insert control. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. The targeted response is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.

C:

Create or apply a supported form template to prepopulate documented fields on compatible records, verify later edits, and avoid confusing a template with a permanent enforcement rule. This approach instead addresses Form templates and controlled record creation. Form templates populate fields for convenience; ACLs, mandatory conditions and business rules govern actual access and persistence. 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: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.

Question 880

Marketing requires a new logo on the self-service portal but the administrator edits a production form label instead. Which configuration or administrative response BEST addresses the primary issue?

  1. Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records.
  2. Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience.
  3. Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance.
  4. Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting.

Explanation

Correct Answer

D:

Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting. Branding surfaces can be configured separately across platform experiences; changing a logo or theme does not modify business rules or application data. Verify prerequisites with: Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies. Scenario: Marketing requires a new logo on the self-service portal but the administrator edits a production form label instead.

Incorrect Answers

A:

Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. This approach instead addresses Related lists and record relationships. A related list is a query-backed view of associated records; it does not inherently store copies of all child rows on the parent. The targeted response is: Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting. Scenario: Marketing requires a new logo on the self-service portal but the administrator edits a production form label instead.

B:

Distinguish personal list columns and form personalization from shared form design or dictionary changes, choosing the least disruptive configuration for the requested audience. This approach instead addresses Per-user list and form personalization. Personalization changes presentation for a user or view; it does not grant access to a protected field or change the underlying table schema. The targeted response is: Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting. Scenario: Marketing requires a new logo on the self-service portal but the administrator edits a production form label instead.

C:

Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance. This approach instead addresses Application installation and plugin activation preflight. Activating a plugin may introduce tables, roles and configuration; it is not equivalent to adding a harmless navigation favorite. The targeted response is: Apply supported branding or portal experience configuration to the intended interface and validate its scope rather than overwriting every workspace or personal preference from one global setting. Scenario: Marketing requires a new logo on the self-service portal but the administrator edits a production form label instead.

ServiceNow Certified System Administrator (CSA) Practice Tests