100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 130
In the scoped Project Intake app handling new project approvals, a form uses a string field to collect a date and users enter ambiguous regional text. Select THREE complementary measures or outcomes that address this case.
- Document input locale and validate boundary dates
- International users store consistent date values and reporting remains correct
- Use a date-appropriate field and test valid input formats
- Keep a free-text string and guess dates in reports
- Make the date field a checkbox
- Hide the field when parsing fails
Explanation
Correct Answers
A:Document input locale and validate boundary dates. It guards against the recurring issue: Field type and input controls affect data validation and consistent storage.
B:Use a date-appropriate field and test valid input formats. This is the direct observed result required before acceptance.
C:Use a date-appropriate field and test valid input formats. The diagnosed cause is: Field type and input controls affect data validation and consistent storage.
Incorrect Answers
D:“Keep a free-text string and guess dates in reports” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
E:“Make the date field a checkbox” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
F:“Hide the field when parsing fails” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
Question 131
In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. What is the most appropriate supported design or corrective action?
- Make the decision field read-only only in the browser
- Create or adjust the field-level write ACL for the decision field
- Allow all writes and audit them later
- Hide the field in one view
Explanation
Correct Answer
B:Create or adjust the field-level write ACL for the decision field. The reason is that write authorization can differ at the table and specific field levels.
Incorrect Answers
A:“Make the decision field read-only only in the browser” would leave the failure unresolved: Write authorization can differ at the table and specific field levels.
C:“Allow all writes and audit them later” would leave the failure unresolved: Write authorization can differ at the table and specific field levels.
D:“Hide the field in one view” would leave the failure unresolved: Write authorization can differ at the table and specific field levels.
Question 132
In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. Which explanation best identifies the underlying ServiceNow application-development problem?
- Creating or changing ACLs can require elevated security_admin privileges; existing protected case records also require backward-compatible behavior
- A field-level ACL may independently restrict access to one attribute; 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
Explanation
Correct Answer
D:Create or adjust the field-level write ACL for the decision field. The underlying issue is that write authorization can differ at the table and specific field levels.
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 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.
B: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: 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 133
In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. After the proposed fix, which observation best proves the requirement was met?
- Unauthorized callers and unrelated attributes receive no data
- The worker edits notes but a direct update to decision is denied
- The tested role either receives the deliberate permission or a documented denial
- Positive and negative access tests reproduce the policy exactly for both old and new protected case records records
Explanation
Correct Answer
B:The worker edits notes but a direct update to decision is denied. This verifies the effect of create or adjust the field-level write ACL for the decision field.
Incorrect Answers
A:This test would assess another concern: In the scoped Application Audits app handling review evidence, a client application reaches an out-of-scope table using a public callable helper that returns excessive columns. It does not verify the stated 3.1 requirement.
C:This test would assess another concern: 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 verify the stated 3.1 requirement.
D:This test would assess another concern: During a change review of the scoped Security Exceptions app used for protected case records, an ACL script contains a check for a specific manager but its condition grants all users on a permissive branch. Previously created protected case records records must remain valid after the change. It does not verify the stated 3.1 requirement.
Question 134
In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test identity changes and role revocations and keep a rollback plan for the Security Exceptions release
- Test read and write operations separately with role impersonation
- Monitor cross-scope privilege changes and review target API exposure and keep a rollback plan for the Facilities Access release
- Inspect helper input, output fields and caller ACLs during review and keep a rollback plan for the Field Safety release
Explanation
Correct Answer
B:Test read and write operations separately with role impersonation. It prevents the following recurring problem: Write authorization can differ at the table and specific field levels.
Incorrect Answers
A:That safeguard addresses a different application 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 control the cause here.
C: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.
D: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.
Question 135
In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. Select TWO complementary measures or outcomes that address this case.
- Create or adjust the field-level write ACL for the decision field
- The worker edits notes but a direct update to decision is denied
- Make the decision field read-only only in the browser
- Allow all writes and audit them later
- Hide the field in one view
Explanation
Correct Answers
A:Create or adjust the field-level write ACL for the decision field. The diagnosed cause is: Write authorization can differ at the table and specific field levels.
B:Create or adjust the field-level write ACL for the decision field. This is the direct observed result required before acceptance.
Incorrect Answers
C:“Make the decision field read-only only in the browser” would leave this failure unresolved: Write authorization can differ at the table and specific field levels.
D:“Allow all writes and audit them later” would leave this failure unresolved: Write authorization can differ at the table and specific field levels.
E:“Hide the field in one view” would leave this failure unresolved: Write authorization can differ at the table and specific field levels.
Question 136
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. What is the most appropriate supported design or corrective action?
- Assume custom action scripts create a subflow trigger
- Disable all flow conditions
- Move the branching orchestration into a subflow and call appropriate actions
- Duplicate entire branches on every form
Explanation
Correct Answer
C:Move the branching orchestration into a subflow and call appropriate actions. The reason is that custom actions handle reusable steps while subflows support reusable branching processes.
Incorrect Answers
A:“Assume custom action scripts create a subflow trigger” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
B:“Disable all flow conditions” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
D:“Duplicate entire branches on every form” would leave the failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
Question 137
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Shared server logic belongs in a reusable Script Include rather than duplicative rule bodies
- Inbound actions need validated sender and payload handling before record mutation; existing incoming workflow emails also require backward-compatible behavior
- Custom actions handle reusable steps while subflows support reusable branching processes
- Configurable application properties separate tunable settings from code; existing incoming workflow emails also require backward-compatible behavior
Explanation
Correct Answer
C:Move the branching orchestration into a subflow and call appropriate actions. The underlying issue is that custom actions handle reusable steps while subflows support reusable branching processes.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Compliance Exceptions app handling policy waivers, several Business Rules copy the same complex eligibility algorithm and produce inconsistent results. It does not explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an inbound email should create a case only when it comes from an authorized sender and matches a recognized format. Previously created incoming workflow emails records must remain valid after the change. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an administrator wants to change an application's notification lead time without editing application scripts. Previously created incoming workflow emails records must remain valid after the change. It does not explain the failure here.
Question 138
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. After the proposed fix, which observation best proves the requirement was met?
- Changing the approved property changes future runs without code edits
- A rejection generates one outbound message with the correct content
- Conditional paths execute as designed using the reusable components
- Unauthorized table names and operations are rejected by the helper
Explanation
Correct Answer
C:Conditional paths execute as designed using the reusable components. This verifies the effect of move the branching orchestration into a subflow and call appropriate actions.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 4.1 requirement.
B:This test would assess another concern: In the scoped Notification Center app handling case email messages, an application sends the same rejection email by both a Flow action and an event-based notification. It does not verify the stated 4.1 requirement.
D:This test would assess another concern: 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 verify the stated 4.1 requirement.
Question 139
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Inventory all notifications and flow email actions for the lifecycle event and keep a rollback plan for the Correspondence Intake release
- Test race conditions between record writes and notification delivery and keep a rollback plan for the Task Automation release
- Test all branch outcomes and action input contracts
- Unit-test the helper and enforce scoped caller permissions and keep a rollback plan for the Grant Applications release
Explanation
Correct Answer
C:Test all branch outcomes and action input contracts. It prevents the following recurring problem: Custom actions handle reusable steps while subflows support reusable branching processes.
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, an application sends the same rejection email by both a Flow action and an event-based notification. 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: During a change review of the scoped Task Automation app used for automated approvals, a workflow sends a status update before the database transaction commits and recipients see stale details. Previously created automated approvals 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 Grant Applications app used for grant reviews, several Business Rules copy the same complex eligibility algorithm and produce inconsistent results. Previously created grant reviews records must remain valid after the change. It does not control the cause here.
Question 140
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. Select THREE complementary measures or outcomes that address this case.
- Test all branch outcomes and action input contracts
- Assume custom action scripts create a subflow trigger
- Duplicate entire branches on every form
- Move the branching orchestration into a subflow and call appropriate actions
- Conditional paths execute as designed using the reusable components
- Disable all flow conditions
Explanation
Correct Answers
A:Test all branch outcomes and action input contracts. It guards against the recurring issue: Custom actions handle reusable steps while subflows support reusable branching processes.
D:Move the branching orchestration into a subflow and call appropriate actions. The diagnosed cause is: Custom actions handle reusable steps while subflows support reusable branching processes.
E:Move the branching orchestration into a subflow and call appropriate actions. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Assume custom action scripts create a subflow trigger” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
C:“Duplicate entire branches on every form” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
F:“Disable all flow conditions” would leave this failure unresolved: Custom actions handle reusable steps while subflows support reusable branching processes.
ServiceNow Certified Application Developer (CAD) Practice Tests