100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 1170
In the scoped Field Safety app handling site-inspection records, a producer script creates the same target record twice after a user retries a slow submission. Select THREE complementary measures or outcomes that address this case.
- Assume all browser submissions occur once
- Monitor duplicate submission keys and test timeout retries
- Validate a stable submission identifier or existing matching target before creating another record
- Use the requestor display name as a unique key
- Remove the record number field
- Retrying the same submission produces one logical record
Explanation
Correct Answers
B:Monitor duplicate submission keys and test timeout retries. It guards against the recurring issue: Duplicate processing and retries need an explicit idempotent submission boundary.
C:Validate a stable submission identifier or existing matching target before creating another record. The diagnosed cause is: Duplicate processing and retries need an explicit idempotent submission boundary.
F:Validate a stable submission identifier or existing matching target before creating another record. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Assume all browser submissions occur once” would leave this failure unresolved: Duplicate processing and retries need an explicit idempotent submission boundary.
D:“Use the requestor display name as a unique key” would leave this failure unresolved: Duplicate processing and retries need an explicit idempotent submission boundary.
E:“Remove the record number field” would leave this failure unresolved: Duplicate processing and retries need an explicit idempotent submission boundary.
Question 1171
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. What is the most appropriate supported design or corrective action?
- Grant every scope read access indefinitely
- Use display-name checks instead of scope identity
- Hide the setting in release notes
- Record the approved consumer and narrow resource privileges before deployment
Explanation
Correct Answer
D:Record the approved consumer and narrow resource privileges before deployment. The reason is that cross-scope access changes introduce dependencies that need owner approval and traceability.
Incorrect Answers
A:“Grant every scope read access indefinitely” would leave the failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
B:“Use display-name checks instead of scope identity” would leave the failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
C:“Hide the setting in release notes” would leave the failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
Question 1172
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Read, write and delete are distinct ACL operations
- Creating or changing ACLs can require elevated security_admin privileges; existing protected case records also require backward-compatible behavior
- Visible navigation does not automatically grant permission to the underlying table
- Cross-scope access changes introduce dependencies that need owner approval and traceability
Explanation
Correct Answer
D:Record the approved consumer and narrow resource privileges before deployment. The underlying issue is that cross-scope access changes introduce dependencies that need owner approval and traceability.
Incorrect Answers
A:This explanation belongs to another app case: 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. 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 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.
C:This explanation belongs to another app case: In the scoped Maintenance Windows app handling planned outages, a requestor cannot open a list even though the module appears in navigation. It does not explain the failure here.
Question 1173
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. After the proposed fix, which observation best proves the requirement was met?
- Unauthorized REST creates fail even if they bypass the portal
- Unauthorized REST creates fail even if they bypass the portal for both old and new automated approvals records
- Audit records identify which scope can read which resource and why
- The denied user's current result matches the updated ACL, with traceable debug output
Explanation
Correct Answer
C:Audit records identify which scope can read which resource and why. This verifies the effect of record the approved consumer and narrow resource privileges before deployment.
Incorrect Answers
A: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.3 requirement.
B:This test would assess another concern: 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. It does not verify the stated 3.3 requirement.
D: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.3 requirement.
Question 1174
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Use Debug Security Rules and field-level allow/deny matrices and keep a rollback plan for the Security Exceptions release
- Require a deny-matrix review for every sensitive custom table
- Test menus and table reads for permitted and denied users
- Revisit cross-scope grants when consumers or application versions change
Explanation
Correct Answer
D:Revisit cross-scope grants when consumers or application versions change. It prevents the following recurring problem: Cross-scope access changes introduce dependencies that need owner approval and traceability.
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 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.
B:That safeguard addresses a different application 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 control the cause here.
C:That safeguard addresses a different application case: In the scoped Training Enrollment app handling course requests, a user sees a confidential case list because the module has a permissive role setting. It does not control the cause here.
Question 1175
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. Select TWO complementary measures or outcomes that address this case.
- Record the approved consumer and narrow resource privileges before deployment
- Audit records identify which scope can read which resource and why
- Hide the setting in release notes
- Use display-name checks instead of scope identity
- Grant every scope read access indefinitely
Explanation
Correct Answers
A:Record the approved consumer and narrow resource privileges before deployment. The diagnosed cause is: Cross-scope access changes introduce dependencies that need owner approval and traceability.
B:Record the approved consumer and narrow resource privileges before deployment. This is the direct observed result required before acceptance.
Incorrect Answers
C:“Hide the setting in release notes” would leave this failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
D:“Use display-name checks instead of scope identity” would leave this failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
E:“Grant every scope read access indefinitely” would leave this failure unresolved: Cross-scope access changes introduce dependencies that need owner approval and traceability.
Question 1176
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. What is the most appropriate supported design or corrective action?
- Create duplicate recipients in a hidden field
- Retain both paths and only change their subject lines
- Suppress message logs instead of eliminating duplicates
- Choose one authoritative notification path or add explicit deduplication
Explanation
Correct Answer
D:Choose one authoritative notification path or add explicit deduplication. The reason is that two independently configured notification paths can duplicate messages.
Incorrect Answers
A:“Create duplicate recipients in a hidden field” would leave the failure unresolved: Two independently configured notification paths can duplicate messages.
B:“Retain both paths and only change their subject lines” would leave the failure unresolved: Two independently configured notification paths can duplicate messages.
C:“Suppress message logs instead of eliminating duplicates” would leave the failure unresolved: Two independently configured notification paths can duplicate messages.
Question 1177
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. 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
- Shared server logic belongs in a reusable Script Include rather than duplicative rule bodies
- Active flows generally use the published action version unless draft usage is explicitly configured; existing automated approvals also require backward-compatible behavior
- Two independently configured notification paths can duplicate messages
Explanation
Correct Answer
D:Choose one authoritative notification path or add explicit deduplication. The underlying issue is that two independently configured notification paths can duplicate messages.
Incorrect Answers
A:This explanation belongs to another app 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 explain the failure here.
B: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.
C:This explanation belongs to another app case: During a change review of the scoped Task Automation app used for automated approvals, a flow does not use the latest published custom action because a modified action remains a draft. Previously created automated approvals records must remain valid after the change. It does not explain the failure here.
Question 1178
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. After the proposed fix, which observation best proves the requirement was met?
- Identical input cases produce matching decisions across the rules for both old and new grant reviews records
- A rejection generates one outbound message with the correct content
- Forced retries create one logical follow-up task for both old and new automated approvals records
- Conditional paths execute as designed using the reusable components
Explanation
Correct Answer
B:A rejection generates one outbound message with the correct content. This verifies the effect of choose one authoritative notification path or add explicit deduplication.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 4.3 requirement.
C:This test would assess another concern: 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. It does not verify the stated 4.3 requirement.
D:This test would assess another concern: 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 verify the stated 4.3 requirement.
Question 1179
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Document trigger frequency, filtering and error retry behavior
- Test absent, malformed and valid property values and keep a rollback plan for the Equipment Loans release
- Set a safe default and restrict who can modify the property
- Inventory all notifications and flow email actions for the lifecycle event
Explanation
Correct Answer
D:Inventory all notifications and flow email actions for the lifecycle event. It prevents the following recurring problem: Two independently configured notification paths can duplicate messages.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Approval Automation app handling request lifecycle, a scheduled flow is configured for a recurring daily trigger but users expect it to run on each new case record. It does not control the cause here.
B:That safeguard addresses a different application 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 control the cause here.
C: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.
Question 1180
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. Select THREE complementary measures or outcomes that address this case.
- Suppress message logs instead of eliminating duplicates
- Choose one authoritative notification path or add explicit deduplication
- A rejection generates one outbound message with the correct content
- Create duplicate recipients in a hidden field
- Inventory all notifications and flow email actions for the lifecycle event
- Retain both paths and only change their subject lines
Explanation
Correct Answers
B:Choose one authoritative notification path or add explicit deduplication. The diagnosed cause is: Two independently configured notification paths can duplicate messages.
C:Choose one authoritative notification path or add explicit deduplication. This is the direct observed result required before acceptance.
E:Inventory all notifications and flow email actions for the lifecycle event. It guards against the recurring issue: Two independently configured notification paths can duplicate messages.
Incorrect Answers
A:“Suppress message logs instead of eliminating duplicates” would leave this failure unresolved: Two independently configured notification paths can duplicate messages.
D:“Create duplicate recipients in a hidden field” would leave this failure unresolved: Two independently configured notification paths can duplicate messages.
F:“Retain both paths and only change their subject lines” would leave this failure unresolved: Two independently configured notification paths can duplicate messages.
ServiceNow Certified Application Developer (CAD) Practice Tests