ServiceNow CAD Exam Dumps, Practice Test Questions

100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!

ServiceNow CAD Premium Bundle
$64.98
$54.98

CAD Premium Bundle

  • Premium File: 218 Questions & Answers. Last update: Nov 7, 2026
  • Training Course: 54 Video Lectures
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

CAD Premium Bundle

ServiceNow CAD Premium Bundle
  • Premium File: 218 Questions & Answers. Last update: Nov 7, 2026
  • Training Course: 54 Video Lectures
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
$64.98
$54.98

ServiceNow CAD Practice Test 87

Question 860

In the scoped Training Enrollment app handling course requests, a shared utility Script Include accepts an arbitrary target table from user-supplied input and updates records. Select THREE complementary measures or outcomes that address this case.

  1. Include negative tests for untrusted parameters
  2. Trust any table passed from a browser
  3. Unauthorized table names and operations are rejected by the helper
  4. Expose the helper anonymously to simplify calls
  5. Whitelist approved tables and validate roles and input before any GlideRecord mutation
  6. Use an elevated service user for all updates

Explanation

Correct Answers

A:

Include negative tests for untrusted parameters. It guards against the recurring issue: Server utilities must validate parameters and enforce intended table and operation boundaries.

C:

Whitelist approved tables and validate roles and input before any GlideRecord mutation. This is the direct observed result required before acceptance.

E:

Whitelist approved tables and validate roles and input before any GlideRecord mutation. The diagnosed cause is: Server utilities must validate parameters and enforce intended table and operation boundaries.

Incorrect Answers

B:

“Trust any table passed from a browser” would leave this failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.

D:

“Expose the helper anonymously to simplify calls” would leave this failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.

F:

“Use an elevated service user for all updates” would leave this failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.

Question 861

During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. What is the most appropriate supported design or corrective action?

  1. Hide all modules for every user without checking existing purchasing records data
  2. Use a different icon as the access control without checking existing purchasing records data
  3. Grant admin to requestors so the link works without checking existing purchasing records data
  4. Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records

Explanation

Correct Answer

D:

Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records. The reason is that navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

Incorrect Answers

A:

“Hide all modules for every user without checking existing purchasing records data” would leave the failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

B:

“Use a different icon as the access control without checking existing purchasing records data” would leave the failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

C:

“Grant admin to requestors so the link works without checking existing purchasing records data” would leave the failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

Question 862

During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?

  1. Independent booleans allow contradictory combinations that a single state would prevent
  2. Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior
  3. Application access distinguishes read, create, update and delete across scopes; existing risk acknowledgments also require backward-compatible behavior
  4. Display names are not reliable primary identifiers for relational joins; existing supplier assessments also require backward-compatible behavior

Explanation

Correct Answer

B:

Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records. The underlying issue is that navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

Incorrect Answers

A:

This explanation belongs to another app case: In the scoped Inventory Transfers app handling movement requests, a request table uses two independent yes/no flags for a single mutually exclusive approval status. It does not explain the failure here.

C:

This explanation belongs to another app case: During a change review of the scoped Security Exceptions app used for risk acknowledgments, an app consumes another scoped table and mistakenly assumes the target table's read settings imply permission to write. Previously created risk acknowledgments records must remain valid after the change. It does not explain the failure here.

D:

This explanation belongs to another app case: During a change review of the scoped Supplier Reviews app used for supplier assessments, a data model references a supplier using the supplier's nonunique trade name, creating collisions between regions. Previously created supplier assessments records must remain valid after the change. It does not explain the failure here.

Question 863

During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?

  1. An approved cross-scope operation succeeds and unauthorized writes remain blocked
  2. A changed display name resolves consistently without rewriting each request
  3. Two similarly named suppliers remain distinct in related records
  4. A requestor does not see the admin module, while a delegated maintainer does for both old and new purchasing records records

Explanation

Correct Answer

D:

A requestor does not see the admin module, while a delegated maintainer does for both old and new purchasing records records. This verifies the effect of restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records.

Incorrect Answers

A:

This test would assess another concern: In the scoped Quality Inspections app handling inspection cases, an app consumes another scoped table and mistakenly assumes the target table's read settings imply permission to write. It does not verify the stated 1.3 requirement.

B:

This test would assess another concern: In the scoped Employee Services app handling staff records, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. It does not verify the stated 1.3 requirement.

C:

This test would assess another concern: In the scoped Vendor Onboarding app handling supplier qualification, a data model references a supplier using the supplier's nonunique trade name, creating collisions between regions. It does not verify the stated 1.3 requirement.

Question 864

During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?

  1. Record the scope and supported deployment route in the design specification
  2. Test duplicates and reference integrity in the sample dataset
  3. Maintain a requirement-to-capability map before creating custom tables
  4. Test navigation role assignments and independently verify data ACLs and keep a rollback plan for the Purchase Approvals release

Explanation

Correct Answer

D:

Test navigation role assignments and independently verify data ACLs and keep a rollback plan for the Purchase Approvals release. It prevents the following recurring problem: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

Incorrect Answers

A:

That safeguard addresses a different application case: In the scoped Visitor Badging app handling temporary credentials, a team starts a new scoped app without checking its name, scope and target instance and later must remap references. It does not control the cause here.

B:

That safeguard addresses a different application case: In the scoped Vendor Onboarding app handling supplier qualification, a data model references a supplier using the supplier's nonunique trade name, creating collisions between regions. It does not control the cause here.

C:

That safeguard addresses a different application case: In the scoped Maintenance Windows app handling planned outages, a developer plans to recreate an existing standard task-management feature as a custom app without checking existing capabilities. It does not control the cause here.

Question 865

During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. Select TWO complementary measures or outcomes that address this case.

  1. Grant admin to requestors so the link works without checking existing purchasing records data
  2. Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records
  3. Use a different icon as the access control without checking existing purchasing records data
  4. Hide all modules for every user without checking existing purchasing records data
  5. A requestor does not see the admin module, while a delegated maintainer does for both old and new purchasing records records

Explanation

Correct Answers

B:

Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records. The diagnosed cause is: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

E:

Restrict the module to an appropriate application administrator role and regression-test the existing purchasing records records. This is the direct observed result required before acceptance.

Incorrect Answers

A:

“Grant admin to requestors so the link works without checking existing purchasing records data” would leave this failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

C:

“Use a different icon as the access control without checking existing purchasing records data” would leave this failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

D:

“Hide all modules for every user without checking existing purchasing records data” would leave this failure unresolved: Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior.

Question 866

During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. What is the most appropriate supported design or corrective action?

  1. Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records
  2. Disable all server-side logic globally without checking existing new project approvals data
  3. Call current.update() again on each recursion without checking existing new project approvals data
  4. Increase timeout to tolerate loops without checking existing new project approvals data

Explanation

Correct Answer

A:

Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records. The reason is that updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

Incorrect Answers

B:

“Disable all server-side logic globally without checking existing new project approvals data” would leave the failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

C:

“Call current.update() again on each recursion without checking existing new project approvals data” would leave the failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

D:

“Increase timeout to tolerate loops without checking existing new project approvals data” would leave the failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

Question 867

During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?

  1. Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior
  2. Direct DOM selectors are fragile across form layouts and platform updates
  3. Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior
  4. Client-side change handling must account for the current state and asynchronous lookup ordering

Explanation

Correct Answer

A:

Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records. The underlying issue is that updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

Incorrect Answers

B:

This explanation belongs to another app case: In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. It does not explain the failure here.

C:

This explanation belongs to another app case: During a change review of the scoped Employee Moves app used for employment requests, a form shows a confidential salary field to the wrong persona because it is placed on the default view. Previously created employment requests records must remain valid after the change. It does not explain the failure here.

D:

This explanation belongs to another app case: In the scoped Supplier Reviews app handling vendor assessments, a form automatically recalculates the wrong field when two dependent choices change rapidly. It does not explain the failure here.

Question 868

During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?

  1. One user update produces the expected final state without repeated executions for both old and new new project approvals records
  2. Invalid submissions are stopped with a clear message, while valid records save
  3. The form receives only the quota decision without leaking restricted rows
  4. International users store consistent date values and reporting remains correct

Explanation

Correct Answer

A:

One user update produces the expected final state without repeated executions for both old and new new project approvals records. This verifies the effect of move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records.

Incorrect Answers

B:

This test would assess another concern: In the scoped Visitor Badging app handling temporary credentials, a submit form must reject invalid overlapping date ranges before save. It does not verify the stated 2.3 requirement.

C:

This test would assess another concern: In the scoped Application Audits app handling review evidence, a developer tries to call GlideRecord directly from a browser script to check a confidential quota. It does not verify the stated 2.3 requirement.

D:

This test would assess another concern: In the scoped Project Intake app handling new project approvals, a form uses a string field to collect a date and users enter ambiguous regional text. It does not verify the stated 2.3 requirement.

Question 869

During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?

  1. Include non-admin API tests in security acceptance criteria and keep a rollback plan for the Lab Reservations release
  2. Use server authorization and avoid unnecessary synchronous calls
  3. Document input locale and validate boundary dates and keep a rollback plan for the Training Enrollment release
  4. Detect recursion and log only bounded rule invocations and keep a rollback plan for the Project Intake release

Explanation

Correct Answer

D:

Detect recursion and log only bounded rule invocations and keep a rollback plan for the Project Intake release. It prevents the following recurring problem: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

Incorrect Answers

A:

That safeguard addresses a different application case: During a change review of the scoped Lab Reservations app used for instrument bookings, a Client Script checks the user's role to hide a sensitive form section. Previously created instrument bookings records must remain valid after the change. It does not control the cause here.

B:

That safeguard addresses a different application case: In the scoped Application Audits app handling review evidence, a developer tries to call GlideRecord directly from a browser script to check a confidential quota. It does not control the cause here.

C:

That safeguard addresses a different application case: During a change review of the scoped Training Enrollment app used for course requests, a form uses a string field to collect a date and users enter ambiguous regional text. Previously created course requests records must remain valid after the change. It does not control the cause here.

Question 870

During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.

  1. Increase timeout to tolerate loops without checking existing new project approvals data
  2. One user update produces the expected final state without repeated executions for both old and new new project approvals records
  3. Detect recursion and log only bounded rule invocations and keep a rollback plan for the Project Intake release
  4. Disable all server-side logic globally without checking existing new project approvals data
  5. Call current.update() again on each recursion without checking existing new project approvals data
  6. Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records

Explanation

Correct Answers

B:

Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records. This is the direct observed result required before acceptance.

C:

Detect recursion and log only bounded rule invocations and keep a rollback plan for the Project Intake release. It guards against the recurring issue: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

F:

Move suitable field changes to before logic or update a different related record carefully and regression-test the existing new project approvals records. The diagnosed cause is: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

Incorrect Answers

A:

“Increase timeout to tolerate loops without checking existing new project approvals data” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

D:

“Disable all server-side logic globally without checking existing new project approvals data” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

E:

“Call current.update() again on each recursion without checking existing new project approvals data” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior.

ServiceNow Certified Application Developer (CAD) Practice Tests

UP

SPECIAL OFFER: GET 10% OFF

This is ONE TIME OFFER

ExamSnap Discount Offer
Enter Your Email Address to Receive Your 10% Off Discount Code

A confirmation link will be sent to this email address to verify your login. *We value your privacy. We will not rent or sell your email address.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.