100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 190
In the scoped Office Relocation app handling move requests, a staff form omits a related list needed to inspect the child's requests. Select THREE complementary measures or outcomes that address this case.
- Copy all child rows into a large text field
- Verify related-list access uses the underlying ACL permissions
- Expose every child regardless of parent
- Replace the relationship with a static URL
- Authorized staff see only the related records for the current parent
- Add the appropriate related list to the intended form view
Explanation
Correct Answers
B:Verify related-list access uses the underlying ACL permissions. It guards against the recurring issue: Related-list placement is form configuration and does not change relationship data.
E:Add the appropriate related list to the intended form view. This is the direct observed result required before acceptance.
F:Add the appropriate related list to the intended form view. The diagnosed cause is: Related-list placement is form configuration and does not change relationship data.
Incorrect Answers
A:“Copy all child rows into a large text field” would leave this failure unresolved: Related-list placement is form configuration and does not change relationship data.
C:“Expose every child regardless of parent” would leave this failure unresolved: Related-list placement is form configuration and does not change relationship data.
D:“Replace the relationship with a static URL” would leave this failure unresolved: Related-list placement is form configuration and does not change relationship data.
Question 191
In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. What is the most appropriate supported design or corrective action?
- Remove the requestor field from the form
- Use list filters as the sole confidentiality boundary
- Ask users not to open other links
- Apply record-aware read restrictions using supported ACL conditions or scripts
Explanation
Correct Answer
D:Apply record-aware read restrictions using supported ACL conditions or scripts. The reason is that a table-level general read ACL may be too broad for record-specific confidentiality.
Incorrect Answers
A:“Remove the requestor field from the form” would leave the failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
B:“Use list filters as the sole confidentiality boundary” would leave the failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
C:“Ask users not to open other links” would leave the failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
Question 192
In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. Which explanation best identifies the underlying ServiceNow application-development problem?
- Admin success may mask the actual effective permissions of non-admin users; existing course requests also require backward-compatible behavior
- Creating application files on foreign tables is controlled by application-access settings; existing movement requests also require backward-compatible behavior
- A table-level general read ACL may be too broad for record-specific confidentiality
- Cross-scope reachability does not replace proper service account roles and endpoint authorization
Explanation
Correct Answer
C:Apply record-aware read restrictions using supported ACL conditions or scripts. The underlying issue is that a table-level general read ACL may be too broad for record-specific confidentiality.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Training Enrollment app used for course requests, an administrator sees a field during testing but an ordinary app user receives an access error. Previously created course requests 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 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 explain the failure here.
D:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, an inbound integration calls a scoped REST endpoint and works in admin tests but fails under its service account. It does not explain the failure here.
Question 193
In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. After the proposed fix, which observation best proves the requirement was met?
- The one required lookup works while unrelated operations are still denied for both old and new relocation checklists records
- Two requestors cannot read each other's protected rows through form or API
- The intended REST request succeeds while unauthorized access still fails for both old and new retirement requests records
- The intended records are visible while the protected attribute remains hidden
Explanation
Correct Answer
B:Two requestors cannot read each other's protected rows through form or API. This verifies the effect of apply record-aware read restrictions using supported ACL conditions or scripts.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Employee Moves app used for relocation checklists, a team's application sets broad cross-scope permissions to solve one failed record lookup. Previously created relocation checklists records must remain valid after the change. It does not verify the stated 3.1 requirement.
C:This test would assess another concern: 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 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 194
In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test the production-like service account rather than only an administrator
- Include row-level unauthorized access tests
- Include non-admin role trials in every access-control review
- Review target ownership and configuration-change history and keep a rollback plan for the Inventory Transfers release
Explanation
Correct Answer
B:Include row-level unauthorized access tests. It prevents the following recurring problem: A table-level general read ACL may be too broad for record-specific confidentiality.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Partner Integrations app handling external data exchange, an inbound integration calls a scoped REST endpoint and works in admin tests but fails under its service account. It does not control the cause here.
C: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.
D: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 195
In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. Select TWO complementary measures or outcomes that address this case.
- Apply record-aware read restrictions using supported ACL conditions or scripts
- Use list filters as the sole confidentiality boundary
- Ask users not to open other links
- Two requestors cannot read each other's protected rows through form or API
- Remove the requestor field from the form
Explanation
Correct Answers
A:Apply record-aware read restrictions using supported ACL conditions or scripts. The diagnosed cause is: A table-level general read ACL may be too broad for record-specific confidentiality.
D:Apply record-aware read restrictions using supported ACL conditions or scripts. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Use list filters as the sole confidentiality boundary” would leave this failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
C:“Ask users not to open other links” would leave this failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
E:“Remove the requestor field from the form” would leave this failure unresolved: A table-level general read ACL may be too broad for record-specific confidentiality.
Question 196
In the scoped Approval Automation app handling request lifecycle, a flow does not use the latest published custom action because a modified action remains a draft. What is the most appropriate supported design or corrective action?
- Publish the reviewed updated action before using it in the active flow
- Rename the draft and assume it deploys
- Delete flow logs to refresh execution
- Change only the action's descriptive label
Explanation
Correct Answer
A:Publish the reviewed updated action before using it in the active flow. The reason is that active flows generally use the published action version unless draft usage is explicitly configured.
Incorrect Answers
B:“Rename the draft and assume it deploys” would leave the failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
C:“Delete flow logs to refresh execution” would leave the failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
D:“Change only the action's descriptive label” would leave the failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
Question 197
In the scoped Approval Automation app handling request lifecycle, a flow does not use the latest published custom action because a modified action remains a draft. Which explanation best identifies the underlying ServiceNow application-development problem?
- Active flows generally use the published action version unless draft usage is explicitly configured
- Two independently configured notification paths can duplicate messages
- Browser events are not suitable for unattended scheduled server operations; existing policy exemptions also require backward-compatible behavior
- Recipient fields and data pills must map to the intended person
Explanation
Correct Answer
A:Publish the reviewed updated action before using it in the active flow. The underlying issue is that active flows generally use the published action version unless draft usage is explicitly configured.
Incorrect Answers
B:This explanation belongs to another app case: 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 explain the failure here.
C:This explanation belongs to another app case: During a change review of the scoped Training Waivers app used for policy exemptions, a monthly review process is implemented as a Client Script that runs only when someone opens the form. Previously created policy exemptions 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 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 198
In the scoped Approval Automation app handling request lifecycle, a flow does not use the latest published custom action because a modified action remains a draft. After the proposed fix, which observation best proves the requirement was met?
- A rejection generates one outbound message with the correct content for both old and new incoming workflow emails records
- Execution details show the expected new action behavior
- The test message appears in expected mail logs and arrives without rejected delivery for both old and new incoming workflow emails records
- A rejection generates one outbound message with the correct content
Explanation
Correct Answer
B:Execution details show the expected new action behavior. This verifies the effect of publish the reviewed updated action before using it in the active flow.
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 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 verify the stated 4.1 requirement.
C:This test would assess another concern: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an outbound notification appears configured but the recipient does not receive it. Previously created incoming workflow emails records must remain valid after the change. It does not verify the stated 4.1 requirement.
D: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.
Question 199
In the scoped Approval Automation app handling request lifecycle, a flow does not use the latest published custom action because a modified action remains a draft. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Check draft/published state during release testing
- Add deliverability monitoring and clear failure logging
- Check event log volume and repeated-save behavior and keep a rollback plan for the Correspondence Intake release
- Include negative tests for untrusted parameters
Explanation
Correct Answer
A:Check draft/published state during release testing. It prevents the following recurring problem: Active flows generally use the published action version unless draft usage is explicitly configured.
Incorrect Answers
B:That safeguard addresses a different application case: 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 control the cause here.
C: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.
D: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 200
In the scoped Approval Automation app handling request lifecycle, a flow does not use the latest published custom action because a modified action remains a draft. Select THREE complementary measures or outcomes that address this case.
- Check draft/published state during release testing
- Delete flow logs to refresh execution
- Execution details show the expected new action behavior
- Publish the reviewed updated action before using it in the active flow
- Change only the action's descriptive label
- Rename the draft and assume it deploys
Explanation
Correct Answers
A:Check draft/published state during release testing. It guards against the recurring issue: Active flows generally use the published action version unless draft usage is explicitly configured.
C:Publish the reviewed updated action before using it in the active flow. This is the direct observed result required before acceptance.
D:Publish the reviewed updated action before using it in the active flow. The diagnosed cause is: Active flows generally use the published action version unless draft usage is explicitly configured.
Incorrect Answers
B:“Delete flow logs to refresh execution” would leave this failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
E:“Change only the action's descriptive label” would leave this failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
F:“Rename the draft and assume it deploys” would leave this failure unresolved: Active flows generally use the published action version unless draft usage is explicitly configured.
ServiceNow Certified Application Developer (CAD) Practice Tests