100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 250
In the scoped Employee Services app handling staff records, a form shows a confidential salary field to the wrong persona because it is placed on the default view. Select THREE complementary measures or outcomes that address this case.
- Send the salary to the client and blur it visually
- Test field visibility and direct data access separately
- Hide the field with CSS alone
- Use an appropriate view and enforce a server-side field read ACL
- Unauthorized roles cannot fetch the salary via form, list or API
- Assume a different form layout is security
Explanation
Correct Answers
B:Test field visibility and direct data access separately. It guards against the recurring issue: Visual placement does not enforce sensitive field access controls.
D:Use an appropriate view and enforce a server-side field read ACL. The diagnosed cause is: Visual placement does not enforce sensitive field access controls.
E:Use an appropriate view and enforce a server-side field read ACL. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Send the salary to the client and blur it visually” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls.
C:“Hide the field with CSS alone” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls.
F:“Assume a different form layout is security” would leave this failure unresolved: Visual placement does not enforce sensitive field access controls.
Question 251
In the scoped Facilities Access app handling building-entry requests, an app manager can read cases but cannot delete them and needs deletion to remain limited. What is the most appropriate supported design or corrective action?
- Delete the record by a Client Script instead
- Hide the Delete button only
- Grant one all-operations ACL to every reader
- Keep read and approved write ACLs while restricting delete to the intended role
Explanation
Correct Answer
D:Keep read and approved write ACLs while restricting delete to the intended role. The reason is that read, write and delete are distinct ACL operations.
Incorrect Answers
A:“Delete the record by a Client Script instead” would leave the failure unresolved: Read, write and delete are distinct ACL operations.
B:“Hide the Delete button only” would leave the failure unresolved: Read, write and delete are distinct ACL operations.
C:“Grant one all-operations ACL to every reader” would leave the failure unresolved: Read, write and delete are distinct ACL operations.
Question 252
In the scoped Facilities Access app handling building-entry requests, an app manager can read cases but cannot delete them and needs deletion to remain limited. Which explanation best identifies the underlying ServiceNow application-development problem?
- Display names are mutable and insufficient as a robust authorization boundary; existing protected case records also require backward-compatible behavior
- Creating or changing ACLs can require elevated security_admin privileges
- Read, write and delete are distinct ACL operations
- Creating application files on foreign tables is controlled by application-access settings
Explanation
Correct Answer
C:Keep read and approved write ACLs while restricting delete to the intended role. The underlying issue is that read, write and delete are distinct ACL operations.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Security Exceptions app used for protected case records, a scripted ACL compares a user's visible full name text as its only authorization identity. Previously created protected case records 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 Access Governance app handling permission reviews, a developer cannot edit Access Control rules despite having the admin role. It does not explain the failure here.
D:This explanation belongs to another app case: 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 explain the failure here.
Question 253
In the scoped Facilities Access app handling building-entry requests, an app manager can read cases but cannot delete them and needs deletion to remain limited. After the proposed fix, which observation best proves the requirement was met?
- The denied user's current result matches the updated ACL, with traceable debug output
- Audit records identify which scope can read which resource and why for both old and new follow-up tasks records
- Renaming a user does not change who can access the record for both old and new protected case records records
- The manager can view records but deletion is blocked without the privileged role
Explanation
Correct Answer
D:The manager can view records but deletion is blocked without the privileged role. This verifies the effect of keep read and approved write ACLs while restricting delete to the intended role.
Incorrect Answers
A:This test would assess another concern: In the scoped Access Governance app handling permission reviews, a new ACL is created but a cached security decision appears to persist during a test. It does not verify the stated 3.1 requirement.
B:This test would assess another concern: 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 verify the stated 3.1 requirement.
C:This test would assess another concern: During a change review of the scoped Security Exceptions app used for protected case records, a scripted ACL compares a user's visible full name text as its only authorization identity. Previously created protected case records records must remain valid after the change. It does not verify the stated 3.1 requirement.
Question 254
In the scoped Facilities Access app handling building-entry requests, an app manager can read cases but cannot delete them and needs deletion to remain limited. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test all CRUD operations under each persona
- Include restricted server-helper calls in security regression tests
- Review target ownership and configuration-change history and keep a rollback plan for the Inventory Transfers release
- Monitor cross-scope privilege changes and review target API exposure
Explanation
Correct Answer
A:Test all CRUD operations under each persona. It prevents the following recurring problem: Read, write and delete are distinct ACL operations.
Incorrect Answers
B:That safeguard addresses a different application case: In the scoped Partner Integrations app handling external data exchange, a custom server helper reads restricted records with ordinary GlideRecord and assumes client ACL checks are enough. It does not control the cause here.
C:That safeguard addresses a different application case: During a change review of the scoped Inventory Transfers app used for movement requests, a scoped app creates a Business Rule on another app's table without approved application access. Previously created movement requests records must remain valid after the change. It does not control the cause here.
D:That safeguard addresses a different application 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 control the cause here.
Question 255
In the scoped Facilities Access app handling building-entry requests, an app manager can read cases but cannot delete them and needs deletion to remain limited. Select TWO complementary measures or outcomes that address this case.
- Grant one all-operations ACL to every reader
- Hide the Delete button only
- Delete the record by a Client Script instead
- The manager can view records but deletion is blocked without the privileged role
- Keep read and approved write ACLs while restricting delete to the intended role
Explanation
Correct Answers
D:Keep read and approved write ACLs while restricting delete to the intended role. This is the direct observed result required before acceptance.
E:Keep read and approved write ACLs while restricting delete to the intended role. The diagnosed cause is: Read, write and delete are distinct ACL operations.
Incorrect Answers
A:“Grant one all-operations ACL to every reader” would leave this failure unresolved: Read, write and delete are distinct ACL operations.
B:“Hide the Delete button only” would leave this failure unresolved: Read, write and delete are distinct ACL operations.
C:“Delete the record by a Client Script instead” would leave this failure unresolved: Read, write and delete are distinct ACL operations.
Question 256
In the scoped Approval Automation app handling request lifecycle, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. What is the most appropriate supported design or corrective action?
- Run fulfillment before checking approval
- Put fulfillment actions behind the approved branch and explicitly handle rejection
- Treat all pending approvals as approved
- Hide the task record after creating it
Explanation
Correct Answer
B:Put fulfillment actions behind the approved branch and explicitly handle rejection. The reason is that branch routing and approval outcome checks determine whether downstream actions run.
Incorrect Answers
A:“Run fulfillment before checking approval” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
C:“Treat all pending approvals as approved” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
D:“Hide the task record after creating it” would leave the failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
Question 257
In the scoped Approval Automation app handling request lifecycle, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Which explanation best identifies the underlying ServiceNow application-development problem?
- Duplicate producers can cause duplicate event-processing side effects
- Scheduled jobs should query only eligible records and track processing state
- Email delivery involves trigger, event, notification condition and mail transport checks
- Branch routing and approval outcome checks determine whether downstream actions run
Explanation
Correct Answer
D:Put fulfillment actions behind the approved branch and explicitly handle rejection. The underlying issue is that branch routing and approval outcome checks determine whether downstream actions run.
Incorrect Answers
A:This explanation belongs to another app case: 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 explain the failure here.
B:This explanation belongs to another app case: In the scoped Site Visits app handling visitor authorizations, a Scheduled Script Execution scans the entire request table every hour and repeatedly reprocesses closed records. 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 outbound notification appears configured but the recipient does not receive it. It does not explain the failure here.
Question 258
In the scoped Approval Automation app handling request lifecycle, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. After the proposed fix, which observation best proves the requirement was met?
- Only approved transitions send the expected message to the requester
- Rejected requests create no fulfillment task and receive the correct outcome
- Only approved transitions send the expected message to the requester for both old and new supplier qualification records
- The app follows the defined fallback when the property is not configured
Explanation
Correct Answer
B:Rejected requests create no fulfillment task and receive the correct outcome. This verifies the effect of put fulfillment actions behind the approved branch and explicitly handle rejection.
Incorrect Answers
A:This test would assess another concern: In the scoped Maintenance Windows app handling planned outages, an app must notify a requester only after the approval outcome becomes Approved. It does not verify the stated 4.1 requirement.
C:This test would assess another concern: 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. It does not verify the stated 4.1 requirement.
D:This test would assess another concern: In the scoped Supplier Reviews app handling vendor assessments, a script calls gs.getProperty for an undefined setting and silently returns an empty value. It does not verify the stated 4.1 requirement.
Question 259
In the scoped Approval Automation app handling request lifecycle, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Set a safe default and restrict who can modify the property
- Test approval and rejection using separate execution traces
- Verify recipient selection for missing or changed references
- Add deliverability monitoring and clear failure logging and keep a rollback plan for the Correspondence Intake release
Explanation
Correct Answer
B:Test approval and rejection using separate execution traces. It prevents the following recurring problem: Branch routing and approval outcome checks determine whether downstream actions run.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Notification Center app handling case email messages, an administrator wants to change an application's notification lead time without editing application scripts. It does not control the cause here.
C:That safeguard addresses a different application case: In the scoped Notification Center app handling case email messages, a notification sends to the record's Assigned to manager instead of the actual requester. It does not control the cause here.
D:That safeguard addresses a different application 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 control the cause here.
Question 260
In the scoped Approval Automation app handling request lifecycle, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Select THREE complementary measures or outcomes that address this case.
- Put fulfillment actions behind the approved branch and explicitly handle rejection
- Test approval and rejection using separate execution traces
- Run fulfillment before checking approval
- Treat all pending approvals as approved
- Rejected requests create no fulfillment task and receive the correct outcome
- Hide the task record after creating it
Explanation
Correct Answers
A:Put fulfillment actions behind the approved branch and explicitly handle rejection. The diagnosed cause is: Branch routing and approval outcome checks determine whether downstream actions run.
B:Test approval and rejection using separate execution traces. It guards against the recurring issue: Branch routing and approval outcome checks determine whether downstream actions run.
E:Put fulfillment actions behind the approved branch and explicitly handle rejection. This is the direct observed result required before acceptance.
Incorrect Answers
C:“Run fulfillment before checking approval” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
D:“Treat all pending approvals as approved” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
F:“Hide the task record after creating it” would leave this failure unresolved: Branch routing and approval outcome checks determine whether downstream actions run.
ServiceNow Certified Application Developer (CAD) Practice Tests