100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 280
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. Select THREE complementary measures or outcomes that address this case.
- Unauthorized roles cannot fetch the salary via form, list or API for both old and new employment requests records
- Test field visibility and direct data access separately and keep a rollback plan for the Employee Moves release
- Send the salary to the client and blur it visually without checking existing employment requests data
- Use an appropriate view and enforce a server-side field read ACL and regression-test the existing employment requests records
- Assume a different form layout is security without checking existing employment requests data
- Hide the field with CSS alone without checking existing employment requests data
Explanation
Correct Answers
A:Use an appropriate view and enforce a server-side field read ACL and regression-test the existing employment requests records. This is the direct observed result required before acceptance.
B:Test field visibility and direct data access separately and keep a rollback plan for the Employee Moves release. It guards against the recurring issue: Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior.
D:Use an appropriate view and enforce a server-side field read ACL and regression-test the existing employment requests records. The diagnosed cause is: Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior.
Incorrect Answers
C:“Send the salary to the client and blur it visually without checking existing employment requests data” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior.
E:“Assume a different form layout is security without checking existing employment requests data” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior.
F:“Hide the field with CSS alone without checking existing employment requests data” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior.
Question 281
During a change review of the scoped Contract Renewals app used for renewal cases, an app manager can read cases but cannot delete them and needs deletion to remain limited. Previously created renewal cases records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Delete the record by a Client Script instead without checking existing renewal cases data
- Hide the Delete button only without checking existing renewal cases data
- Grant one all-operations ACL to every reader without checking existing renewal cases data
- Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records
Explanation
Correct Answer
D:Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records. The reason is that read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
Incorrect Answers
A:“Delete the record by a Client Script instead without checking existing renewal cases data” would leave the failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
B:“Hide the Delete button only without checking existing renewal cases data” would leave the failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
C:“Grant one all-operations ACL to every reader without checking existing renewal cases data” would leave the failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
Question 282
During a change review of the scoped Contract Renewals app used for renewal cases, an app manager can read cases but cannot delete them and needs deletion to remain limited. Previously created renewal cases records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- A resource may block cross-scope invocation despite the user's record roles
- Cross-scope reachability does not replace proper service account roles and endpoint authorization
- Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior
- Cross-scope access changes introduce dependencies that need owner approval and traceability; existing follow-up tasks also require backward-compatible behavior
Explanation
Correct Answer
C:Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records. The underlying issue is that read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Facilities Repairs app handling repair requests, a private scoped app calls a protected Script Include from another app and receives a cross-scope access error. It does not explain the failure here.
B:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, an inbound integration calls a scoped REST endpoint and works in admin tests but fails under its service account. 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 developer changes application scope settings to grant third-party read access but does not document the consumer. Previously created follow-up tasks records must remain valid after the change. It does not explain the failure here.
Question 283
During a change review of the scoped Contract Renewals app used for renewal cases, an app manager can read cases but cannot delete them and needs deletion to remain limited. Previously created renewal cases records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- Users holding only one privilege are denied the protected action for both old and new protected case records records
- The intended REST request succeeds while unauthorized access still fails
- The manager can view records but deletion is blocked without the privileged role for both old and new renewal cases records
- Only authorized scopes can attach new server logic to the protected table
Explanation
Correct Answer
C:The manager can view records but deletion is blocked without the privileged role for both old and new renewal cases records. This verifies the effect of keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Security Exceptions app used for protected case records, an ACL allows access when the user has one of two roles but the policy requires both approval and finance privileges. Previously created protected case records records must remain valid after the change. It does not verify the stated 3.1 requirement.
B:This test would assess another concern: In the scoped Vendor Onboarding app handling supplier qualification, a table's web-services access is blocked although cross-scope scripts can read its records. It does not verify the stated 3.1 requirement.
D:This test would assess another concern: In the scoped Visitor Badging app handling temporary credentials, a scoped app creates a Business Rule on another app's table without approved application access. It does not verify the stated 3.1 requirement.
Question 284
During a change review of the scoped Contract Renewals app used for renewal cases, an app manager can read cases but cannot delete them and needs deletion to remain limited. Previously created renewal cases records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test all CRUD operations under each persona and keep a rollback plan for the Contract Renewals release
- Monitor cross-scope privilege changes and review target API exposure and keep a rollback plan for the Facilities Access release
- Use Debug Security Rules and field-level allow/deny matrices
- Include non-admin role trials in every access-control review
Explanation
Correct Answer
A:Test all CRUD operations under each persona and keep a rollback plan for the Contract Renewals release. It prevents the following recurring problem: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
Incorrect Answers
B:That safeguard addresses a different application case: During a change review of the scoped Facilities Access app used for building-entry requests, a private scoped app calls a protected Script Include from another app and receives a cross-scope access error. Previously created building-entry requests records must remain valid after the change. It does not control the cause here.
C:That safeguard addresses a different application case: In the scoped Access Governance app handling permission reviews, a field ACL denies read access but an analyst tests only table read permissions. It does not control the cause here.
D:That safeguard addresses a different application case: In the scoped Project Intake app handling new project approvals, an administrator sees a field during testing but an ordinary app user receives an access error. It does not control the cause here.
Question 285
During a change review of the scoped Contract Renewals app used for renewal cases, an app manager can read cases but cannot delete them and needs deletion to remain limited. Previously created renewal cases records must remain valid after the change. Select TWO complementary measures or outcomes that address this case.
- Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records
- Grant one all-operations ACL to every reader without checking existing renewal cases data
- Hide the Delete button only without checking existing renewal cases data
- The manager can view records but deletion is blocked without the privileged role for both old and new renewal cases records
- Delete the record by a Client Script instead without checking existing renewal cases data
Explanation
Correct Answers
A:Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records. The diagnosed cause is: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
D:Keep read and approved write ACLs while restricting delete to the intended role and regression-test the existing renewal cases records. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Grant one all-operations ACL to every reader without checking existing renewal cases data” would leave this failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
C:“Hide the Delete button only without checking existing renewal cases data” would leave this failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
E:“Delete the record by a Client Script instead without checking existing renewal cases data” would leave this failure unresolved: Read, write and delete are distinct ACL operations; existing renewal cases also require backward-compatible behavior.
Question 286
During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Treat all pending approvals as approved without checking existing automated approvals data
- Hide the task record after creating it without checking existing automated approvals data
- Run fulfillment before checking approval without checking existing automated approvals data
- Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records
Explanation
Correct Answer
D:Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records. The reason is that branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:“Treat all pending approvals as approved without checking existing automated approvals data” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
B:“Hide the task record after creating it without checking existing automated approvals data” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
C:“Run fulfillment before checking approval without checking existing automated approvals data” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
Question 287
During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- Email delivery involves trigger, event, notification condition and mail transport checks; existing incoming workflow emails also require backward-compatible behavior
- Registered event names and their consumers must match exactly
- Inbound processing must identify the target conversation or record
- Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior
Explanation
Correct Answer
D:Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records. The underlying issue is that branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an outbound notification appears configured but the recipient does not receive it. Previously created incoming workflow emails records must remain valid after the change. It does not explain the failure here.
B:This explanation belongs to another app case: In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped Notification Center app handling case email messages, an inbound email replies to an existing case but the system creates a duplicate instead of correlating it. It does not explain the failure here.
Question 288
During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- A reply adds information to the correct existing case without duplicates for both old and new incoming workflow emails records
- Rejected requests create no fulfillment task and receive the correct outcome for both old and new automated approvals records
- The test message appears in expected mail logs and arrives without rejected delivery for both old and new incoming workflow emails records
- One qualifying transition produces one intended event
Explanation
Correct Answer
B:Rejected requests create no fulfillment task and receive the correct outcome for both old and new automated approvals records. This verifies the effect of put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an inbound email replies to an existing case but the system creates a duplicate instead of correlating it. Previously created incoming workflow emails records must remain valid after the change. It does not verify the stated 4.1 requirement.
C:This test would assess another concern: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an outbound notification appears configured but the recipient does not receive it. Previously created incoming workflow emails records must remain valid after the change. It does not verify the stated 4.1 requirement.
D:This test would assess another concern: In the scoped Notification Center app handling case email messages, an event-driven notification fires twice after a request is saved because two scripts enqueue the same event. It does not verify the stated 4.1 requirement.
Question 289
During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Verify recipient selection for missing or changed references and keep a rollback plan for the Correspondence Intake release
- Include negative tests for untrusted parameters
- Validate event registry entries and tests during application deployment and keep a rollback plan for the Correspondence Intake release
- Test approval and rejection using separate execution traces and keep a rollback plan for the Task Automation release
Explanation
Correct Answer
D:Test approval and rejection using separate execution traces and keep a rollback plan for the Task Automation release. It prevents the following recurring problem: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, a notification sends to the record's Assigned to manager instead of the actual requester. Previously created incoming workflow emails 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 Training Enrollment app handling course requests, a shared utility Script Include accepts an arbitrary target table from user-supplied input and updates records. It does not control the cause here.
C:That safeguard addresses a different application case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, a script triggers an event but no notification occurs because the event name is misspelled. Previously created incoming workflow emails records must remain valid after the change. It does not control the cause here.
Question 290
During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Rejected requests create no fulfillment task and receive the correct outcome for both old and new automated approvals records
- Run fulfillment before checking approval without checking existing automated approvals data
- Hide the task record after creating it without checking existing automated approvals data
- Treat all pending approvals as approved without checking existing automated approvals data
- Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records
- Test approval and rejection using separate execution traces and keep a rollback plan for the Task Automation release
Explanation
Correct Answers
A:Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records. This is the direct observed result required before acceptance.
E:Put fulfillment actions behind the approved branch and explicitly handle rejection and regression-test the existing automated approvals records. The diagnosed cause is: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
F:Test approval and rejection using separate execution traces and keep a rollback plan for the Task Automation release. It guards against the recurring issue: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
B:“Run fulfillment before checking approval without checking existing automated approvals data” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
C:“Hide the task record after creating it without checking existing automated approvals data” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
D:“Treat all pending approvals as approved without checking existing automated approvals data” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run; existing automated approvals also require backward-compatible behavior.
ServiceNow Certified Application Developer (CAD) Practice Tests