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 79

Question 780

A technician moves between groups but continues to have a sensitive inherited role through another membership. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Critical settings and access grants have attributable approved changes and stale privileges are removed after review.
  2. The designated user performs only approved duties, and a nonmember account cannot access the restricted management action.
  3. The script reads or changes only intended records with approved permission boundaries and predictable performance.
  4. Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities.

Explanation

Correct Answer

B:

The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. Roles control capabilities while groups often organize work and confer roles; assignment to a task group does not inherently grant all administrator privileges. Scenario: A technician moves between groups but continues to have a sensitive inherited role through another membership.

Incorrect Answers

A:

Critical settings and access grants have attributable approved changes and stale privileges are removed after review. This result would support Audit and accountability for privileged instance operations, not the specific outcome required in the case. The relevant acceptance test is: The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. Scenario: A technician moves between groups but continues to have a sensitive inherited role through another membership.

C:

The script reads or changes only intended records with approved permission boundaries and predictable performance. This result would support GlideRecord server-side query and secure result handling, not the specific outcome required in the case. The relevant acceptance test is: The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. Scenario: A technician moves between groups but continues to have a sensitive inherited role through another membership.

D:

Security configuration is changed by an authorized elevated account and ordinary sessions do not retain unnecessary administrator capabilities. This result would support Elevated security administration and role boundaries, not the specific outcome required in the case. The relevant acceptance test is: The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. Scenario: A technician moves between groups but continues to have a sensitive inherited role through another membership.

Question 781

Incident impact is overreported because every application server is marked as a separate business service without dependency links. Which configuration or administrative response BEST addresses the primary issue?

  1. Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration.
  2. 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.
  3. Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact.
  4. Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact.

Explanation

Correct Answer

C:

Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. CSDM provides consistent service modeling conventions, not a single generic CI class into which all offerings and applications should be placed. Verify prerequisites with: Inspect intended service model, CSDM class definitions, offering consumers, dependency topology and CMDB relationship direction. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

Incorrect Answers

A:

Use supported CMDB identification and reconciliation rules for merging authorized discovery data, ensuring one CI is not duplicated or overwritten by a lower-trust integration. This approach instead addresses CMDB Identification and Reconciliation Engine source trust. Identification and reconciliation distinguish an existing CI from a new one and govern conflicting data sources; a generic coalesce map alone may be insufficient for CMDB integrity. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

B:

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. This approach instead addresses Platform analytics as a reporting capability. Analytics provides views of governed source data, not a replacement for the underlying record lifecycle or ACL model. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

D:

Design application-scope permissions and cross-scope access explicitly for supported integrations while keeping data table ACLs and role checks intact. This approach instead addresses Scoped application permissions and cross-scope access. Application scope boundaries and user-level ACLs are separate checks; a cross-scope grant does not automatically make table data public. The targeted response is: Apply CSDM guidance to distinguish business services, technical services, service offerings and application services, keeping relationships consistent for service impact. Scenario: Incident impact is overreported because every application server is marked as a separate business service without dependency links.

Question 782

An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection. 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 server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects.
  3. 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.
  4. Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment.

Explanation

Correct Answer

C:

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. Client scripts cannot call every server API directly; supported server endpoints must validate untrusted request parameters independently. Verify prerequisites with: Inspect client script invocation, callable Script Include scope, input parameter validation, authenticated user, ACLs, and returned payload shape. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

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: 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. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

B:

Use supported server-side GlideRecord operations with narrow queries, controlled updates and required user authorization, avoiding unbounded full-table scans and unaudited side effects. This approach instead addresses GlideRecord server-side query and secure result handling. GlideRecord is a server-side record API; code correctness and secure user-level data access are separate concerns requiring enforcement. The targeted response is: 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. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

D:

Use an approval action and an explicit wait/resumption condition for long-running decisions, ensuring rejection and cancellation paths are handled without premature fulfillment. This approach instead addresses Flow approvals and wait-for-condition boundaries. Waiting for approval is a durable lifecycle state; successful notification delivery and final approval are separate events. The targeted response is: 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. Scenario: An asynchronous reference lookup returns after a user changes the field, and a stale callback overwrites the newer selection.

Question 783

An external integration sends restricted ticket descriptions to a third party without reviewing the data-sharing policy. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation.
  2. Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
  3. Inspect the user's selected view, personalized column order, form layout rules, required fields, and whether the change is global or per-user.
  4. Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability.

Explanation

Correct Answer

D:

Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. The appropriate response is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Scenario: An external integration sends restricted ticket descriptions to a third party without reviewing the data-sharing policy.

Incorrect Answers

A:

Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. This evidence is relevant to Shared responsibility between ServiceNow and customer administrators, not the most diagnostic first check for this failure. Examine: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: An external integration sends restricted ticket descriptions to a third party without reviewing the data-sharing policy.

B:

Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. This evidence is relevant to Audit and accountability for privileged instance operations, not the most diagnostic first check for this failure. Examine: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: An external integration sends restricted ticket descriptions to a third party without reviewing the data-sharing policy.

C:

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 record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: An external integration sends restricted ticket descriptions to a third party without reviewing the data-sharing policy.

Question 784

A reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Inspect finding source, policy scope, severity, affected asset, false positive evidence, owner, and remediation verification.
  2. Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs.
  3. The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning.
  4. Handle security posture exceptions through explicit owner approval, documented compensating controls and recurring review, rather than suppressing an uncomfortable warning forever.
  5. 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.

Explanation

Correct Answers

A:

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 reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

E:

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 reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

Incorrect Answers

B:

Inspect reference table, dictionary field type, display field configuration, target record identity, qualifiers and read ACLs. This step may apply to Reference fields and display values in the data dictionary but is not one of the complementary requirements in this case. The intended pair is: 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 reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

C:

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: 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 reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

D:

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 reported control violation affects an app outside the team's scope but gets assigned to the wrong owner without evidence.

Question 785

New hires need a laptop, software license and building access from one onboarding submission. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task.
  2. The field accepts valid values and preserves existing data, while controlled errors prevent unintended data loss from an incompatible type change.
  3. Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names.
  4. One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements.

Explanation

Correct Answer

D:

One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements. A request can contain multiple requested items; the order-guide experience should not collapse independent approvals or ownership into an untracked generic task. Scenario: New hires need a laptop, software license and building access from one onboarding submission.

Incorrect Answers

A:

An unresolved interaction transfers the necessary verified context to an authorized support agent or creates a traceable follow-up task. This result would support Virtual Agent human handoff and fallback, not the specific outcome required in the case. The relevant acceptance test is: One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements. Scenario: New hires need a laptop, software license and building access from one onboarding submission.

B:

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: One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements. Scenario: New hires need a laptop, software license and building access from one onboarding submission.

C:

Two different calling flows obtain consistent bounded outputs without depending on a specific parent record's field names. This result would support Reusable subflows and defined input output contracts, not the specific outcome required in the case. The relevant acceptance test is: One guided order produces the correct eligible requested items and respective fulfillment paths without duplicates or hidden requirements. Scenario: New hires need a laptop, software license and building access from one onboarding submission.

Question 786

A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval.
  2. Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls.
  3. Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs.
  4. Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior.

Explanation

Correct Answer

B:

Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Unconditional current.update() from within a Business Rule may cause recursion; explicit conditions and lifecycle choice matter. The appropriate 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 Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

Incorrect Answers

A:

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 triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

C:

Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs. This evidence is relevant to Business Rule timing and before after async display behavior, not the most diagnostic first check for this failure. Examine: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

D:

Inspect variable reference table, qualifier conditions, criteria, active records, caller identity and ACL behavior. This evidence is relevant to Catalog item reference qualifier and eligibility, not the most diagnostic first check for this failure. Examine: Inspect triggering operations, current/previous field comparisons, rule order, repeated record updates, and downstream event or flow calls. Scenario: A Business Rule updates its own current record after every update and repeatedly triggers itself until execution limits are reached.

Question 787

An incident form should require a resolution code only when State changes to Resolved, but the code stays mandatory for New incidents. 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 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.
  3. 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.
  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

B:

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: An incident form should require a resolution code only when State changes to Resolved, but the code stays mandatory for New incidents.

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: 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: An incident form should require a resolution code only when State changes to Resolved, but the code stays mandatory for New incidents.

C:

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: An incident form should require a resolution code only when State changes to Resolved, but the code stays mandatory for New incidents.

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 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: An incident form should require a resolution code only when State changes to Resolved, but the code stays mandatory for New incidents.

Question 788

An application is visible in the store but an administrator assumes its listing proves the organization's subscription permits all features. Before changing the configuration, which evidence should the administrator examine FIRST?

  1. Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records.
  2. Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance.
  3. Review available themes, portal branding configuration, workspace branding support, accessible color contrast, change scope and instance policies.
  4. Inspect application scope, current update set, captured customer update records, dependency ordering, target release, preview problems and deployment approval.

Explanation

Correct Answer

B:

Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance. Activating a plugin may introduce tables, roles and configuration; it is not equivalent to adding a harmless navigation favorite. The appropriate response is: Assess required ServiceNow applications, plugins, dependencies, licensing/entitlements and target release support before installing or activating functionality on a production instance. Scenario: An application is visible in the store but an administrator assumes its listing proves the organization's subscription permits all features.

Incorrect Answers

A:

Check underlying table, form view, list conditions, required roles, workspace target and navigation context before editing records. This evidence is relevant to Core platform lists versus forms and workspaces, not the most diagnostic first check for this failure. Examine: Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance. Scenario: An application is visible in the store but an administrator assumes its listing proves the organization's subscription permits all features.

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: Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance. Scenario: An application is visible in the store but an administrator assumes its listing proves the organization's subscription permits all features.

D:

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: Review the application/plugin state, vendor prerequisites, activation side effects, subscription rights, upgrade compatibility, and rollback or support guidance. Scenario: An application is visible in the store but an administrator assumes its listing proves the organization's subscription permits all features.

Question 789

An administrator removes a required field from a form layout and believes the underlying database requirement is gone. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?

  1. Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls.
  2. The filtered list includes the intended cases and excludes representative counterexamples without exposing unreadable records.
  3. A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values.
  4. The intended users see the approved form field order while role-based access and record data remain intact.

Explanation

Correct Answer

D:

The intended users see the approved form field order while role-based access and record data remain intact. A form view controls field presentation; it cannot safely replace field-level ACL checks or enforce all server-side data requirements. Scenario: An administrator removes a required field from a form layout and believes the underlying database requirement is gone.

Incorrect Answers

A:

Users can navigate logically grouped form sections and save records without hidden mandatory-field failures or missing controls. This result would support Form sections and related layout configuration, not the specific outcome required in the case. The relevant acceptance test is: The intended users see the approved form field order while role-based access and record data remain intact. Scenario: An administrator removes a required field from a form layout and believes the underlying database requirement is gone.

B:

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: The intended users see the approved form field order while role-based access and record data remain intact. Scenario: An administrator removes a required field from a form layout and believes the underlying database requirement is gone.

C:

A requester can submit valid data, receives actionable required-field feedback, and fulfillment records contain correct variable values. This result would support Service Catalog item variables and validation, not the specific outcome required in the case. The relevant acceptance test is: The intended users see the approved form field order while role-based access and record data remain intact. Scenario: An administrator removes a required field from a form layout and believes the underlying database requirement is gone.

Question 790

A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.

  1. Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete.
  2. Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution.
  3. Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience.
  4. Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history.
  5. A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data.

Explanation

Correct Answers

A:

Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. Verify prerequisites with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.

B:

Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. A successful activation message reports a deployment outcome but not end-to-end permission or business-process correctness. The appropriate response is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.

Incorrect Answers

C:

Use the UI appropriate to bulk record filtering, single-record editing, or guided workspace tasks, preserving actual authorization across the experience. This step may apply to Core platform lists versus forms and workspaces but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.

D:

Inspect property name/value/type, owning application, upgrade/clone behavior, dependent code, cache effects, and audit history. This step may apply to Instance properties and scoped configuration control but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.

E:

A record producer creates the intended case or task record and a fulfillment item follows its configured request/RITM flow without misrouting data. This step may apply to Record producer versus catalog item selection but is not one of the complementary requirements in this case. The intended pair is: Validate an activated ServiceNow plugin's intended feature in a supported test instance, including created modules, security and integrations, before considering the enablement complete. Together with: Inspect plugin activation status, instance version, installed dependencies, new table ACLs, default roles, and sample workflow execution. Scenario: A plugin activation shows Success but a newly added flow action cannot run because an associated role was omitted.

ServiceNow Certified System Administrator (CSA) Practice Tests