100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 920
During a change review of the scoped Vendor Onboarding app used for supplier qualification, an app must notify a requester only after the approval outcome becomes Approved. Previously created supplier qualification records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Use a form help text as the message sender without checking existing supplier qualification data
- Send the message on every form load without checking existing supplier qualification data
- Mail all application users regardless of role without checking existing supplier qualification data
- Trigger the notification on the approved transition or a specific event and regression-test the existing supplier qualification records
- Test nonapproval updates and recipient resolution and keep a rollback plan for the Vendor Onboarding release
- Only approved transitions send the expected message to the requester for both old and new supplier qualification records
Explanation
Correct Answers
D:Trigger the notification on the approved transition or a specific event and regression-test the existing supplier qualification records. The diagnosed cause is: Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior.
E:Test nonapproval updates and recipient resolution and keep a rollback plan for the Vendor Onboarding release. It guards against the recurring issue: Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior.
F:Trigger the notification on the approved transition or a specific event and regression-test the existing supplier qualification records. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Use a form help text as the message sender without checking existing supplier qualification data” would leave this failure unresolved: Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior.
B:“Send the message on every form load without checking existing supplier qualification data” would leave this failure unresolved: Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior.
C:“Mail all application users regardless of role without checking existing supplier qualification data” would leave this failure unresolved: Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior.
Question 921
In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. What is the most appropriate supported design or corrective action?
- Rely on hidden navigation alone
- Obfuscate the table name
- Keep module role restrictions and enforce underlying table and field ACLs
- Assume a nonindexed module cannot be reached
Explanation
Correct Answer
C:Keep module role restrictions and enforce underlying table and field ACLs. The reason is that navigation hiding is not a substitute for record- and operation-level authorization.
Incorrect Answers
A:“Rely on hidden navigation alone” would leave the failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
B:“Obfuscate the table name” would leave the failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
D:“Assume a nonindexed module cannot be reached” would leave the failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
Question 922
In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. Which explanation best identifies the underlying ServiceNow application-development problem?
- Early scope and environment decisions affect code identifiers and application deployment
- A good platform fit still requires role-specific access and least privilege; existing automated approvals also require backward-compatible behavior
- Navigation hiding is not a substitute for record- and operation-level authorization
- Uncontrolled text permits inconsistent categories and unreliable aggregation; existing permit requests also require backward-compatible behavior
Explanation
Correct Answer
C:Keep module role restrictions and enforce underlying table and field ACLs. The underlying issue is that navigation hiding is not a substitute for record- and operation-level authorization.
Incorrect Answers
A:This explanation belongs to another app 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 explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Task Automation app used for automated approvals, a request workflow must be accessible to approvers and submitters, but the proposal gives everyone the admin role. Previously created automated approvals 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 Work Permit Intake app used for permit requests, reports group the same category as different values because free-text entries vary in spelling. Previously created permit requests records must remain valid after the change. It does not explain the failure here.
Question 923
In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. After the proposed fix, which observation best proves the requirement was met?
- Direct-link attempts by unauthorized users fail to retrieve protected data
- Reporting computes totals correctly and rejects malformed amounts
- Only permitted statuses occur and reports group requests consistently
- Two similarly named suppliers remain distinct in related records for both old and new supplier assessments records
Explanation
Correct Answer
A:Direct-link attempts by unauthorized users fail to retrieve protected data. This verifies the effect of keep module role restrictions and enforce underlying table and field ACLs.
Incorrect Answers
B:This test would assess another concern: In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. It does not verify the stated 1.3 requirement.
C:This test would assess another concern: 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 verify the stated 1.3 requirement.
D:This test would assess another concern: 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 verify the stated 1.3 requirement.
Question 924
In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Maintain a requirement-to-capability map before creating custom tables and keep a rollback plan for the Vendor Onboarding release
- Review personas, data ownership and privilege boundaries at design time
- Specify relationship cardinality and deletion behavior before schema changes
- Test both navigation visibility and direct access under non-admin roles
Explanation
Correct Answer
D:Test both navigation visibility and direct access under non-admin roles. It prevents the following recurring problem: Navigation hiding is not a substitute for record- and operation-level authorization.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Vendor Onboarding app used for supplier qualification, a developer plans to recreate an existing standard task-management feature as a custom app without checking existing capabilities. Previously created supplier qualification 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 Approval Automation app handling request lifecycle, a request workflow must be accessible to approvers and submitters, but the proposal gives everyone the admin role. It does not control the cause here.
C:That safeguard addresses a different application case: In the scoped Security Exceptions app handling risk acknowledgments, a review record must link to many evidence documents and each document can support many reviews. It does not control the cause here.
Question 925
In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. Select TWO complementary measures or outcomes that address this case.
- Assume a nonindexed module cannot be reached
- Keep module role restrictions and enforce underlying table and field ACLs
- Rely on hidden navigation alone
- Obfuscate the table name
- Direct-link attempts by unauthorized users fail to retrieve protected data
Explanation
Correct Answers
B:Keep module role restrictions and enforce underlying table and field ACLs. The diagnosed cause is: Navigation hiding is not a substitute for record- and operation-level authorization.
E:Keep module role restrictions and enforce underlying table and field ACLs. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Assume a nonindexed module cannot be reached” would leave this failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
C:“Rely on hidden navigation alone” would leave this failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
D:“Obfuscate the table name” would leave this failure unresolved: Navigation hiding is not a substitute for record- and operation-level authorization.
Question 926
In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. What is the most appropriate supported design or corrective action?
- Use a narrow condition or changesTo / changes guard for the intended transition
- Turn off audit history
- Check the change only by visible form color
- Send the notification for every field edit
Explanation
Correct Answer
A:Use a narrow condition or changesTo / changes guard for the intended transition. The reason is that unrestricted Business Rule conditions cause unnecessary actions and duplicates.
Incorrect Answers
B:“Turn off audit history” would leave the failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
C:“Check the change only by visible form color” would leave the failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
D:“Send the notification for every field edit” would leave the failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
Question 927
In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. Which explanation best identifies the underlying ServiceNow application-development problem?
- Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior
- An onChange handler can run during loading and should avoid unnecessary server calls; existing retirement requests also require backward-compatible behavior
- Unrestricted Business Rule conditions cause unnecessary actions and duplicates
- Direct DOM selectors are fragile across form layouts and platform updates; existing follow-up tasks also require backward-compatible behavior
Explanation
Correct Answer
C:Use a narrow condition or changesTo / changes guard for the intended transition. The underlying issue is that unrestricted Business Rule conditions cause unnecessary actions and duplicates.
Incorrect Answers
A: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.
B:This explanation belongs to another app case: During a change review of the scoped Asset Disposal app used for retirement requests, an onChange Client Script performs an expensive lookup every time the form initially loads. Previously created retirement requests 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 Incident Follow-ups app used for follow-up tasks, a browser script needs the current table field value but accesses an unsupported raw DOM selector. Previously created follow-up tasks records must remain valid after the change. It does not explain the failure here.
Question 928
In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. After the proposed fix, which observation best proves the requirement was met?
- Unauthorized roles cannot fetch the salary via form, list or API for both old and new employment requests records
- Changing Emergency on and off updates the required field consistently for both old and new building-entry requests records
- Only the targeted state transition triggers the associated server action
- The form receives only the quota decision without leaking restricted rows for both old and new site-inspection records records
Explanation
Correct Answer
C:Only the targeted state transition triggers the associated server action. This verifies the effect of use a narrow condition or changesTo / changes guard for the intended transition.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 2.3 requirement.
B:This test would assess another concern: During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. It does not verify the stated 2.3 requirement.
D:This test would assess another concern: During a change review of the scoped Field Safety app used for site-inspection records, a developer tries to call GlideRecord directly from a browser script to check a confidential quota. Previously created site-inspection records records must remain valid after the change. It does not verify the stated 2.3 requirement.
Question 929
In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Monitor duplicate submission keys and test timeout retries
- Test nonmatching updates and repeated saves for idempotency
- Include non-admin API tests in security acceptance criteria and keep a rollback plan for the Lab Reservations release
- Run conflict tests and document authoritative field-control rules and keep a rollback plan for the Employee Moves release
Explanation
Correct Answer
B:Test nonmatching updates and repeated saves for idempotency. It prevents the following recurring problem: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Field Safety app handling site-inspection records, a producer script creates the same target record twice after a user retries a slow submission. It does not control the cause here.
C: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.
D:That safeguard addresses a different application case: During a change review of the scoped Employee Moves app used for relocation checklists, a UI Policy conflicts with a Client Script over the same field's visibility and behaves unexpectedly. Previously created relocation checklists records must remain valid after the change. It does not control the cause here.
Question 930
In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. Select THREE complementary measures or outcomes that address this case.
- Test nonmatching updates and repeated saves for idempotency
- Only the targeted state transition triggers the associated server action
- Send the notification for every field edit
- Check the change only by visible form color
- Turn off audit history
- Use a narrow condition or changesTo / changes guard for the intended transition
Explanation
Correct Answers
A:Test nonmatching updates and repeated saves for idempotency. It guards against the recurring issue: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
B:Use a narrow condition or changesTo / changes guard for the intended transition. This is the direct observed result required before acceptance.
F:Use a narrow condition or changesTo / changes guard for the intended transition. The diagnosed cause is: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
Incorrect Answers
C:“Send the notification for every field edit” would leave this failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
D:“Check the change only by visible form color” would leave this failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
E:“Turn off audit history” would leave this failure unresolved: Unrestricted Business Rule conditions cause unnecessary actions and duplicates.
ServiceNow Certified Application Developer (CAD) Practice Tests