100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 850
In the scoped Work Permit Intake app handling permit requests, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Select THREE complementary measures or outcomes that address this case.
- Increase timeout to tolerate loops
- Move suitable field changes to before logic or update a different related record carefully
- Detect recursion and log only bounded rule invocations
- One user update produces the expected final state without repeated executions
- Disable all server-side logic globally
- Call current.update() again on each recursion
Explanation
Correct Answers
B:Move suitable field changes to before logic or update a different related record carefully. The diagnosed cause is: Updating the same record in an after rule can recursively trigger Business Rules.
C:Detect recursion and log only bounded rule invocations. It guards against the recurring issue: Updating the same record in an after rule can recursively trigger Business Rules.
D:Move suitable field changes to before logic or update a different related record carefully. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Increase timeout to tolerate loops” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules.
E:“Disable all server-side logic globally” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules.
F:“Call current.update() again on each recursion” would leave this failure unresolved: Updating the same record in an after rule can recursively trigger Business Rules.
Question 851
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. What is the most appropriate supported design or corrective action?
- Infer success from an old debug icon
- Delete unrelated client scripts
- Assume caches never affect evaluation traces
- Run a controlled ACL debug session and verify effective decisions after cache refresh where required
Explanation
Correct Answer
D:Run a controlled ACL debug session and verify effective decisions after cache refresh where required. The reason is that security debugging must distinguish cached ACL outcomes and current policy changes.
Incorrect Answers
A:“Infer success from an old debug icon” would leave the failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
B:“Delete unrelated client scripts” would leave the failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
C:“Assume caches never affect evaluation traces” would leave the failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
Question 852
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Security debugging must distinguish cached ACL outcomes and current policy changes
- Web-services access and script database permissions are separate configuration surfaces; existing retirement requests also require backward-compatible behavior
- Role assignment and group membership must be evaluated for the actual logged-in user
- Scope isolation alone does not guarantee correctly configured record-level ACLs
Explanation
Correct Answer
A:Run a controlled ACL debug session and verify effective decisions after cache refresh where required. The underlying issue is that security debugging must distinguish cached ACL outcomes and current policy changes.
Incorrect Answers
B:This explanation belongs to another app case: During a change review of the scoped Asset Disposal app used for retirement requests, a table's web-services access is blocked although cross-scope scripts can read its records. Previously created retirement requests records must remain valid after the change. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. It does not explain the failure here.
D:This explanation belongs to another app case: In the scoped Field Safety app handling site-inspection records, a sensitive table is copied into a new scope with default permissive access settings. It does not explain the failure here.
Question 853
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. 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
- Two requestors cannot read each other's protected rows through form or API for both old and new review evidence records
- Unauthorized REST creates fail even if they bypass the portal
- The scoped service identity invokes only its approved endpoint operations for both old and new partner record synchronization records
Explanation
Correct Answer
A:The denied user's current result matches the updated ACL, with traceable debug output. This verifies the effect of run a controlled ACL debug session and verify effective decisions after cache refresh where required.
Incorrect Answers
B:This test would assess another concern: During a change review of the scoped Application Audits app used for review evidence, a requester should see only their own application records, not all records in the table. Previously created review evidence records must remain valid after the change. It does not verify the stated 3.2 requirement.
C:This test would assess another concern: In the scoped Approval Automation app handling request lifecycle, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. It does not verify the stated 3.2 requirement.
D:This test would assess another concern: During a change review of the scoped Integration Reviews app used for partner record synchronization, an inbound integration calls a scoped REST endpoint and works in admin tests but fails under its service account. Previously created partner record synchronization records must remain valid after the change. It does not verify the stated 3.2 requirement.
Question 854
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Revisit cross-scope grants when consumers or application versions change
- Inspect helper input, output fields and caller ACLs during review and keep a rollback plan for the Field Safety release
- Record cache and impersonation state during security tests
- Include role-provisioning diagnostics in onboarding tests
Explanation
Correct Answer
C:Record cache and impersonation state during security tests. It prevents the following recurring problem: Security debugging must distinguish cached ACL outcomes and current policy changes.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Fleet Maintenance app handling vehicle-service approvals, a developer changes application scope settings to grant third-party read access but does not document the consumer. It does not control the cause here.
B:That safeguard addresses a different application case: During a change review of the scoped Field Safety app used for site-inspection records, a client application reaches an out-of-scope table using a public callable helper that returns excessive columns. Previously created site-inspection records 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 Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. It does not control the cause here.
Question 855
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. Select TWO complementary measures or outcomes that address this case.
- Delete unrelated client scripts
- Assume caches never affect evaluation traces
- Infer success from an old debug icon
- Run a controlled ACL debug session and verify effective decisions after cache refresh where required
- The denied user's current result matches the updated ACL, with traceable debug output
Explanation
Correct Answers
D:Run a controlled ACL debug session and verify effective decisions after cache refresh where required. The diagnosed cause is: Security debugging must distinguish cached ACL outcomes and current policy changes.
E:Run a controlled ACL debug session and verify effective decisions after cache refresh where required. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Delete unrelated client scripts” would leave this failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
B:“Assume caches never affect evaluation traces” would leave this failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
C:“Infer success from an old debug icon” would leave this failure unresolved: Security debugging must distinguish cached ACL outcomes and current policy changes.
Question 856
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. What is the most appropriate supported design or corrective action?
- Whitelist approved tables and validate roles and input before any GlideRecord mutation
- Expose the helper anonymously to simplify calls
- Use an elevated service user for all updates
- Trust any table passed from a browser
Explanation
Correct Answer
A:Whitelist approved tables and validate roles and input before any GlideRecord mutation. The reason is that server utilities must validate parameters and enforce intended table and operation boundaries.
Incorrect Answers
B:“Expose the helper anonymously to simplify calls” would leave the failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.
C:“Use an elevated service user for all updates” would leave the failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.
D:“Trust any table passed from a browser” would leave the failure unresolved: Server utilities must validate parameters and enforce intended table and operation boundaries.
Question 857
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- A repeated flow action can cause duplicated external or record side effects
- Custom actions handle reusable steps while subflows support reusable branching processes
- Notification timing must match the persisted and approved business state
- Server utilities must validate parameters and enforce intended table and operation boundaries
Explanation
Correct Answer
D:Whitelist approved tables and validate roles and input before any GlideRecord mutation. The underlying issue is that server utilities must validate parameters and enforce intended table and operation boundaries.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Approval Automation app handling request lifecycle, a flow retries after a timeout and creates duplicate follow-up tasks. It does not explain the failure here.
B:This explanation belongs to another app case: In the scoped Facilities Repairs app handling repair requests, a developer makes a custom action with script steps but attempts to place conditional branching logic directly inside the action. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped Approval Automation app handling request lifecycle, a workflow sends a status update before the database transaction commits and recipients see stale details. It does not explain the failure here.
Question 858
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. After the proposed fix, which observation best proves the requirement was met?
- A recipient receives only the permitted status information
- Only qualifying status changes start a new flow execution for both old and new automated approvals records
- Unauthorized table names and operations are rejected by the helper
- Conditional paths execute as designed using the reusable components for both old and new building-entry requests records
Explanation
Correct Answer
C:Unauthorized table names and operations are rejected by the helper. This verifies the effect of whitelist approved tables and validate roles and input before any GlideRecord mutation.
Incorrect Answers
A:This test would assess another concern: In the scoped Notification Center app handling case email messages, a notification template includes confidential investigation notes visible to an external recipient. It does not verify the stated 4.2 requirement.
B:This test would assess another concern: During a change review of the scoped Task Automation app used for automated approvals, a flow should start when an approval request changes to Ready but runs on unrelated edits. Previously created automated approvals records must remain valid after the change. It does not verify the stated 4.2 requirement.
D:This test would assess another concern: During a change review of the scoped Facilities Access app used for building-entry requests, a developer makes a custom action with script steps but attempts to place conditional branching logic directly inside the action. Previously created building-entry requests records must remain valid after the change. It does not verify the stated 4.2 requirement.
Question 859
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test all branch outcomes and action input contracts
- Include negative tests for untrusted parameters
- Test nonapproval updates and recipient resolution and keep a rollback plan for the Vendor Onboarding release
- Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release
Explanation
Correct Answer
B:Include negative tests for untrusted parameters. It prevents the following recurring problem: Server utilities must validate parameters and enforce intended table and operation boundaries.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Facilities Repairs app handling repair requests, a developer makes a custom action with script steps but attempts to place conditional branching logic directly inside the action. It does not control the cause here.
C:That safeguard addresses a different application case: 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 control the cause here.
D:That safeguard addresses a different application case: During a change review of the scoped Facilities Access app used for building-entry requests, a developer makes a custom action with script steps but attempts to place conditional branching logic directly inside the action. Previously created building-entry requests records must remain valid after the change. It does not control the cause here.
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.
- Include negative tests for untrusted parameters
- Trust any table passed from a browser
- Unauthorized table names and operations are rejected by the helper
- Expose the helper anonymously to simplify calls
- Whitelist approved tables and validate roles and input before any GlideRecord mutation
- 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.
ServiceNow Certified Application Developer (CAD) Practice Tests