100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 340
During a change review of the scoped Security Exceptions app used for risk acknowledgments, a developer needs a default value for a classification field but hard-codes it in several form scripts. Previously created risk acknowledgments records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Set a governed field default or appropriately centralized creation logic and regression-test the existing risk acknowledgments records
- Ask users to retype the default every time without checking existing risk acknowledgments data
- Test create paths and avoid duplicate conflicting defaults and keep a rollback plan for the Security Exceptions release
- Set default in a tooltip without checking existing risk acknowledgments data
- Rely on form order to choose a data value without checking existing risk acknowledgments data
- Records created by form and automation receive consistent defaults for both old and new risk acknowledgments records
Explanation
Correct Answers
A:Set a governed field default or appropriately centralized creation logic and regression-test the existing risk acknowledgments records. The diagnosed cause is: Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior.
C:Test create paths and avoid duplicate conflicting defaults and keep a rollback plan for the Security Exceptions release. It guards against the recurring issue: Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior.
F:Set a governed field default or appropriately centralized creation logic and regression-test the existing risk acknowledgments records. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Ask users to retype the default every time without checking existing risk acknowledgments data” would leave this failure unresolved: Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior.
D:“Set default in a tooltip without checking existing risk acknowledgments data” would leave this failure unresolved: Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior.
E:“Rely on form order to choose a data value without checking existing risk acknowledgments data” would leave this failure unresolved: Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior.
Question 341
During a change review of the scoped Task Automation app used for automated approvals, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. Previously created automated approvals records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Rely on the portal form's submit button role without checking existing automated approvals data
- Trust the browser's disabled field values without checking existing automated approvals data
- Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records
- Assume an obscure endpoint is safe without checking existing automated approvals data
Explanation
Correct Answer
C:Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records. The reason is that uI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:“Rely on the portal form's submit button role without checking existing automated approvals data” would leave the failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
B:“Trust the browser's disabled field values without checking existing automated approvals data” would leave the failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
D:“Assume an obscure endpoint is safe without checking existing automated approvals data” would leave the failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
Question 342
During a change review of the scoped Task Automation app used for automated approvals, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. Previously created automated approvals records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- A field-level ACL may independently restrict access to one attribute; existing protected case records also require backward-compatible behavior
- UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior
- Creating or changing ACLs can require elevated security_admin privileges; existing protected case records also require backward-compatible behavior
- Admin success may mask the actual effective permissions of non-admin users
Explanation
Correct Answer
B:Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records. The underlying issue is that uI experience does not replace create-operation authorization; 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 Security Exceptions app used for protected case records, a field ACL denies read access but an analyst tests only table read permissions. Previously created protected case records records must remain valid after the change. 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 protected case records, a developer cannot edit Access Control rules despite having the admin role. Previously created protected case records 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 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 explain the failure here.
Question 343
During a change review of the scoped Task Automation app used for automated approvals, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. Previously created automated approvals records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- The one required lookup works while unrelated operations are still denied
- Unauthorized REST creates fail even if they bypass the portal for both old and new automated approvals records
- The authorized maintainer can save the ACL while ordinary admins cannot alter it
- The intended records are visible while the protected attribute remains hidden
Explanation
Correct Answer
B:Unauthorized REST creates fail even if they bypass the portal for both old and new automated approvals records. This verifies the effect of enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records.
Incorrect Answers
A:This test would assess another concern: In the scoped Contract Renewals app handling renewal cases, a team's application sets broad cross-scope permissions to solve one failed record lookup. It does not verify the stated 3.1 requirement.
C:This test would assess another concern: In the scoped Access Governance app handling permission reviews, a developer cannot edit Access Control rules despite having the admin role. It does not verify the stated 3.1 requirement.
D:This test would assess another concern: 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 verify the stated 3.1 requirement.
Question 344
During a change review of the scoped Task Automation app used for automated approvals, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. Previously created automated approvals records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Include restricted server-helper calls in security regression tests and keep a rollback plan for the Integration Reviews release
- Run non-UI create attempts in acceptance testing and keep a rollback plan for the Task Automation release
- Test identity changes and role revocations
- Include non-admin role trials in every access-control review
Explanation
Correct Answer
B:Run non-UI create attempts in acceptance testing and keep a rollback plan for the Task Automation release. It prevents the following recurring problem: UI experience does not replace create-operation authorization; 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 Integration Reviews app used for partner record synchronization, a custom server helper reads restricted records with ordinary GlideRecord and assumes client ACL checks are enough. Previously created partner record synchronization 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 scripted ACL compares a user's visible full name text as its only authorization identity. 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 345
During a change review of the scoped Task Automation app used for automated approvals, a workflow creates a new record from a Service Portal submission but unauthorized users can insert the same record through an API. Previously created automated approvals records must remain valid after the change. Select TWO complementary measures or outcomes that address this case.
- Trust the browser's disabled field values without checking existing automated approvals data
- Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records
- Rely on the portal form's submit button role without checking existing automated approvals data
- Assume an obscure endpoint is safe without checking existing automated approvals data
- Unauthorized REST creates fail even if they bypass the portal for both old and new automated approvals records
Explanation
Correct Answers
B:Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records. The diagnosed cause is: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
E:Enforce a table create ACL and server-side validation for the intended role and regression-test the existing automated approvals records. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Trust the browser's disabled field values without checking existing automated approvals data” would leave this failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
C:“Rely on the portal form's submit button role without checking existing automated approvals data” would leave this failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
D:“Assume an obscure endpoint is safe without checking existing automated approvals data” would leave this failure unresolved: UI experience does not replace create-operation authorization; existing automated approvals also require backward-compatible behavior.
Question 346
During a change review of the scoped Task Automation app used for automated approvals, a flow retries after a timeout and creates duplicate follow-up tasks. Previously created automated approvals records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Suppress execution logs instead of deduplicating without checking existing automated approvals data
- Insert a new task on every retry without checking existing automated approvals data
- Treat duplicate task numbers as harmless without checking existing automated approvals data
- Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records
Explanation
Correct Answer
D:Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records. The reason is that a repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:“Suppress execution logs instead of deduplicating without checking existing automated approvals data” would leave the failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
B:“Insert a new task on every retry without checking existing automated approvals data” would leave the failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
C:“Treat duplicate task numbers as harmless without checking existing automated approvals data” would leave the failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
Question 347
During a change review of the scoped Task Automation app used for automated approvals, a flow retries after a timeout and creates duplicate follow-up tasks. Previously created automated approvals records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- Notification triggers should reflect the actual event or transition rather than every save; existing supplier qualification also require backward-compatible behavior
- A missing application property can require a deliberate fallback value; existing borrowed assets also require backward-compatible behavior
- Server utilities must validate parameters and enforce intended table and operation boundaries; existing repair requests also require backward-compatible behavior
- A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior
Explanation
Correct Answer
D:Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records. The underlying issue is that a repeated flow action can cause duplicated external or record side effects; 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 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 explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Equipment Loans app used for borrowed assets, a script calls gs.getProperty for an undefined setting and silently returns an empty value. Previously created borrowed assets records must remain valid after the change. It does not explain the failure here.
C:This explanation belongs to another app case: During a change review of the scoped Facilities Repairs app used for repair requests, a shared utility Script Include accepts an arbitrary target table from user-supplied input and updates records. Previously created repair requests records must remain valid after the change. It does not explain the failure here.
Question 348
During a change review of the scoped Task Automation app used for automated approvals, a flow retries after a timeout and creates duplicate follow-up tasks. 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
- The app follows the defined fallback when the property is not configured
- Forced retries create one logical follow-up task for both old and new automated approvals records
- Subsequent runs act only on new eligible records
Explanation
Correct Answer
C:Forced retries create one logical follow-up task for both old and new automated approvals records. This verifies the effect of implement stable deduplication or idempotent task creation with explicit retry handling 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.
B: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.
D:This test would assess another concern: 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 verify the stated 4.1 requirement.
Question 349
During a change review of the scoped Task Automation app used for automated approvals, a flow retries after a timeout and creates duplicate follow-up tasks. Previously created automated approvals records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Document scheduling, time zones and missed-run handling
- Measure job duration and alert on unexpected volume
- Include negative tests for untrusted parameters
- Test failure injection and repeated trigger events and keep a rollback plan for the Task Automation release
Explanation
Correct Answer
D:Test failure injection and repeated trigger events and keep a rollback plan for the Task Automation release. It prevents the following recurring problem: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Purchase Approvals app handling purchasing records, a monthly review process is implemented as a Client Script that runs only when someone opens the form. It does not control the cause here.
B:That safeguard addresses a different application 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 control the cause here.
C: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.
Question 350
During a change review of the scoped Task Automation app used for automated approvals, a flow retries after a timeout and creates duplicate follow-up tasks. Previously created automated approvals records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Treat duplicate task numbers as harmless without checking existing automated approvals data
- Forced retries create one logical follow-up task for both old and new automated approvals records
- Suppress execution logs instead of deduplicating without checking existing automated approvals data
- Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records
- Insert a new task on every retry without checking existing automated approvals data
- Test failure injection and repeated trigger events and keep a rollback plan for the Task Automation release
Explanation
Correct Answers
B:Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records. This is the direct observed result required before acceptance.
D:Implement stable deduplication or idempotent task creation with explicit retry handling and regression-test the existing automated approvals records. The diagnosed cause is: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
F:Test failure injection and repeated trigger events and keep a rollback plan for the Task Automation release. It guards against the recurring issue: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
Incorrect Answers
A:“Treat duplicate task numbers as harmless without checking existing automated approvals data” would leave this failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
C:“Suppress execution logs instead of deduplicating without checking existing automated approvals data” would leave this failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
E:“Insert a new task on every retry without checking existing automated approvals data” would leave this failure unresolved: A repeated flow action can cause duplicated external or record side effects; existing automated approvals also require backward-compatible behavior.
ServiceNow Certified Application Developer (CAD) Practice Tests