100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 160
During a change review of the scoped Training Enrollment app used for course requests, a form uses a string field to collect a date and users enter ambiguous regional text. Previously created course requests records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Keep a free-text string and guess dates in reports without checking existing course requests data
- Use a date-appropriate field and test valid input formats and regression-test the existing course requests records
- Hide the field when parsing fails without checking existing course requests data
- Make the date field a checkbox without checking existing course requests data
- International users store consistent date values and reporting remains correct for both old and new course requests records
- Document input locale and validate boundary dates and keep a rollback plan for the Training Enrollment release
Explanation
Correct Answers
B:Use a date-appropriate field and test valid input formats and regression-test the existing course requests records. The diagnosed cause is: Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior.
E:Use a date-appropriate field and test valid input formats and regression-test the existing course requests records. This is the direct observed result required before acceptance.
F:Document input locale and validate boundary dates and keep a rollback plan for the Training Enrollment release. It guards against the recurring issue: Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior.
Incorrect Answers
A:“Keep a free-text string and guess dates in reports without checking existing course requests data” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior.
C:“Hide the field when parsing fails without checking existing course requests data” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior.
D:“Make the date field a checkbox without checking existing course requests data” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior.
Question 161
During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Allow all writes and audit them later without checking existing temporary credentials data
- Hide the field in one view without checking existing temporary credentials data
- Make the decision field read-only only in the browser without checking existing temporary credentials data
- Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records
Explanation
Correct Answer
D:Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records. The reason is that write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
Incorrect Answers
A:“Allow all writes and audit them later without checking existing temporary credentials data” would leave the failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
B:“Hide the field in one view without checking existing temporary credentials data” would leave the failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
C:“Make the decision field read-only only in the browser without checking existing temporary credentials data” would leave the failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
Question 162
During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- Server-side scripts require explicit attention to access enforcement and trusted execution context
- Security debugging must distinguish cached ACL outcomes and current policy changes; existing protected case records also require backward-compatible behavior
- Blanket privilege expansion increases accidental access and maintenance risk
- Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior
Explanation
Correct Answer
D:Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records. The underlying issue is that write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app 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 explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Security Exceptions app used for protected case records, a new ACL is created but a cached security decision appears to persist during a test. 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: 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 explain the failure here.
Question 163
During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- The worker edits notes but a direct update to decision is denied for both old and new temporary credentials records
- The one required lookup works while unrelated operations are still denied
- Audit records identify which scope can read which resource and why
- Unauthorized callers and unrelated attributes receive no data for both old and new site-inspection records records
Explanation
Correct Answer
A:The worker edits notes but a direct update to decision is denied for both old and new temporary credentials records. This verifies the effect of create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records.
Incorrect Answers
B: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 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 verify the stated 3.1 requirement.
D:This test would assess another concern: 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 verify the stated 3.1 requirement.
Question 164
During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Include non-admin role trials in every access-control review
- Use Debug Security Rules and field-level allow/deny matrices and keep a rollback plan for the Security Exceptions release
- Review target ownership and configuration-change history and keep a rollback plan for the Inventory Transfers release
- Test read and write operations separately with role impersonation and keep a rollback plan for the Visitor Badging release
Explanation
Correct Answer
D:Test read and write operations separately with role impersonation and keep a rollback plan for the Visitor Badging release. It prevents the following recurring problem: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
Incorrect Answers
A: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.
B:That safeguard addresses a different application 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 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.
Question 165
During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. Select TWO complementary measures or outcomes that address this case.
- Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records
- Make the decision field read-only only in the browser without checking existing temporary credentials data
- Allow all writes and audit them later without checking existing temporary credentials data
- The worker edits notes but a direct update to decision is denied for both old and new temporary credentials records
- Hide the field in one view without checking existing temporary credentials data
Explanation
Correct Answers
A:Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records. The diagnosed cause is: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
D:Create or adjust the field-level write ACL for the decision field and regression-test the existing temporary credentials records. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Make the decision field read-only only in the browser without checking existing temporary credentials data” would leave this failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
C:“Allow all writes and audit them later without checking existing temporary credentials data” would leave this failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
E:“Hide the field in one view without checking existing temporary credentials data” would leave this failure unresolved: Write authorization can differ at the table and specific field levels; existing temporary credentials also require backward-compatible behavior.
Question 166
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. What is the most appropriate supported design or corrective action?
- Duplicate entire branches on every form without checking existing building-entry requests data
- Assume custom action scripts create a subflow trigger without checking existing building-entry requests data
- Disable all flow conditions without checking existing building-entry requests data
- Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records
Explanation
Correct Answer
D:Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records. The reason is that custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
A:“Duplicate entire branches on every form without checking existing building-entry requests data” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
B:“Assume custom action scripts create a subflow trigger without checking existing building-entry requests data” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
C:“Disable all flow conditions without checking existing building-entry requests data” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
Question 167
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior
- Recipient fields and data pills must map to the intended person; existing incoming workflow emails also require backward-compatible behavior
- Duplicate producers can cause duplicate event-processing side effects
- Recipient fields and data pills must map to the intended person
Explanation
Correct Answer
A:Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records. The underlying issue is that custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
B:This explanation belongs to another app 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 explain the failure here.
C: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.
D:This explanation belongs to another app 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 explain the failure here.
Question 168
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. After the proposed fix, which observation best proves the requirement was met?
- The app follows the defined fallback when the property is not configured for both old and new borrowed assets records
- The task runs at the planned schedule without a user visiting a form
- The test message appears in expected mail logs and arrives without rejected delivery
- Conditional paths execute as designed using the reusable components for both old and new building-entry requests records
Explanation
Correct Answer
D:Conditional paths execute as designed using the reusable components for both old and new building-entry requests records. This verifies the effect of move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 4.1 requirement.
B:This test would assess another concern: 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 verify the stated 4.1 requirement.
C:This test would assess another concern: 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 verify the stated 4.1 requirement.
Question 169
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release
- Check event log volume and repeated-save behavior and keep a rollback plan for the Correspondence Intake release
- Verify recipient selection for missing or changed references
- Test spoofed headers and malformed payloads
Explanation
Correct Answer
A:Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release. It prevents the following recurring problem: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
B:That safeguard addresses a different application case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an event-driven notification fires twice after a request is saved because two scripts enqueue the same event. Previously created incoming workflow emails 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 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: In the scoped Notification Center app handling case email messages, an inbound email should create a case only when it comes from an authorized sender and matches a recognized format. It does not control the cause here.
Question 170
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. Select THREE complementary measures or outcomes that address this case.
- Duplicate entire branches on every form without checking existing building-entry requests data
- Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records
- Conditional paths execute as designed using the reusable components for both old and new building-entry requests records
- Disable all flow conditions without checking existing building-entry requests data
- Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release
- Assume custom action scripts create a subflow trigger without checking existing building-entry requests data
Explanation
Correct Answers
B:Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records. The diagnosed cause is: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
C:Move the branching orchestration into a subflow and call appropriate actions and regression-test the existing building-entry requests records. This is the direct observed result required before acceptance.
E:Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release. It guards against the recurring issue: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
A:“Duplicate entire branches on every form without checking existing building-entry requests data” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
D:“Disable all flow conditions without checking existing building-entry requests data” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
F:“Assume custom action scripts create a subflow trigger without checking existing building-entry requests data” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes; existing building-entry requests also require backward-compatible behavior.
ServiceNow Certified Application Developer (CAD) Practice Tests