100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 810
In the scoped Compliance Exceptions app handling policy waivers, a before Business Rule should populate a derived approval category but writes only to a local variable. Select THREE complementary measures or outcomes that address this case.
- Assign the derived value to the current record field in the appropriate before rule
- Write the value into a browser-only variable
- Test on insert and update with the correct trigger condition
- Call current.update() inside the same before rule
- Use a notification template as storage
- The saved record includes the derived category without an extra self-update
Explanation
Correct Answers
A:Assign the derived value to the current record field in the appropriate before rule. The diagnosed cause is: Before Business Rules can modify current fields prior to persistence.
C:Test on insert and update with the correct trigger condition. It guards against the recurring issue: Before Business Rules can modify current fields prior to persistence.
F:Assign the derived value to the current record field in the appropriate before rule. This is the direct observed result required before acceptance.
Incorrect Answers
B:“Write the value into a browser-only variable” would leave this failure unresolved: Before Business Rules can modify current fields prior to persistence.
D:“Call current.update() inside the same before rule” would leave this failure unresolved: Before Business Rules can modify current fields prior to persistence.
E:“Use a notification template as storage” would leave this failure unresolved: Before Business Rules can modify current fields prior to persistence.
Question 811
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. What is the most appropriate supported design or corrective action?
- Return all fields and ask callers not to display secrets
- Move confidential data into client-side g_form
- Trust any sys_id passed from the browser
- Use appropriate server-side access validation and GlideRecordSecure where suitable
Explanation
Correct Answer
D:Use appropriate server-side access validation and GlideRecordSecure where suitable. The reason is that server-side scripts require explicit attention to access enforcement and trusted execution context.
Incorrect Answers
A:“Return all fields and ask callers not to display secrets” would leave the failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
B:“Move confidential data into client-side g_form” would leave the failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
C:“Trust any sys_id passed from the browser” would leave the failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
Question 812
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Creating application files on foreign tables is controlled by application-access settings; existing movement requests also require backward-compatible behavior
- Server-side scripts require explicit attention to access enforcement and trusted execution context
- A resource may block cross-scope invocation despite the user's record roles
- Scope isolation alone does not guarantee correctly configured record-level ACLs
Explanation
Correct Answer
B:Use appropriate server-side access validation and GlideRecordSecure where suitable. The underlying issue is that server-side scripts require explicit attention to access enforcement and trusted execution context.
Incorrect Answers
A: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.
C:This explanation belongs to another app case: In the scoped Facilities Repairs app handling repair requests, a private scoped app calls a protected Script Include from another app and receives a cross-scope access error. It does not explain the failure here.
D:This explanation belongs to another app 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 explain the failure here.
Question 813
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. After the proposed fix, which observation best proves the requirement was met?
- The worker edits notes but a direct update to decision is denied
- The scoped service identity invokes only its approved endpoint operations
- Unauthorized helper callers cannot obtain protected records or fields
- A properly authorized requestor can read permitted rows without admin rights
Explanation
Correct Answer
C:Unauthorized helper callers cannot obtain protected records or fields. This verifies the effect of use appropriate server-side access validation and GlideRecordSecure where suitable.
Incorrect Answers
A:This test would assess another concern: In the scoped Service Requests app handling internal support requests, a case worker may edit notes but should not change the protected approval decision. It does not verify the stated 3.2 requirement.
B:This test would assess another concern: 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 verify the stated 3.2 requirement.
D:This test would assess another concern: 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 verify the stated 3.2 requirement.
Question 814
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Include restricted server-helper calls in security regression tests
- Audit API exposure and operation-specific ACLs
- Run non-UI create attempts in acceptance testing
- Inspect helper input, output fields and caller ACLs during review and keep a rollback plan for the Field Safety release
Explanation
Correct Answer
A:Include restricted server-helper calls in security regression tests. It prevents the following recurring problem: Server-side scripts require explicit attention to access enforcement and trusted execution context.
Incorrect Answers
B:That safeguard addresses a different application case: In the scoped Vendor Onboarding app handling supplier qualification, a table's web-services access is blocked although cross-scope scripts can read its records. It does not control the cause here.
C:That safeguard addresses a different application case: 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 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 815
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. Select TWO complementary measures or outcomes that address this case.
- Return all fields and ask callers not to display secrets
- Trust any sys_id passed from the browser
- Move confidential data into client-side g_form
- Use appropriate server-side access validation and GlideRecordSecure where suitable
- Unauthorized helper callers cannot obtain protected records or fields
Explanation
Correct Answers
D:Use appropriate server-side access validation and GlideRecordSecure where suitable. The diagnosed cause is: Server-side scripts require explicit attention to access enforcement and trusted execution context.
E:Use appropriate server-side access validation and GlideRecordSecure where suitable. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Return all fields and ask callers not to display secrets” would leave this failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
B:“Trust any sys_id passed from the browser” would leave this failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
C:“Move confidential data into client-side g_form” would leave this failure unresolved: Server-side scripts require explicit attention to access enforcement and trusted execution context.
Question 816
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. What is the most appropriate supported design or corrective action?
- Filter by status and a durable last-processed or eligibility criterion
- Run a query without conditions each hour
- Turn off logging to reduce database load
- Reset processed flags on every run
Explanation
Correct Answer
A:Filter by status and a durable last-processed or eligibility criterion. The reason is that scheduled jobs should query only eligible records and track processing state.
Incorrect Answers
B:“Run a query without conditions each hour” would leave the failure unresolved: Scheduled jobs should query only eligible records and track processing state.
C:“Turn off logging to reduce database load” would leave the failure unresolved: Scheduled jobs should query only eligible records and track processing state.
D:“Reset processed flags on every run” would leave the failure unresolved: Scheduled jobs should query only eligible records and track processing state.
Question 817
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Scheduled jobs should query only eligible records and track processing state
- Record-trigger conditions must identify the relevant record transition or state
- Date triggers and record triggers respond to different lifecycle events; existing automated approvals also require backward-compatible behavior
- Two independently configured notification paths can duplicate messages
Explanation
Correct Answer
A:Filter by status and a durable last-processed or eligibility criterion. The underlying issue is that scheduled jobs should query only eligible records and track processing state.
Incorrect Answers
B:This explanation belongs to another app case: In the scoped Approval Automation app handling request lifecycle, a flow should start when an approval request changes to Ready but runs on unrelated edits. 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 scheduled flow is configured for a recurring daily trigger but users expect it to run on each new case record. Previously created automated approvals 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, an application sends the same rejection email by both a Flow action and an event-based notification. It does not explain the failure here.
Question 818
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. After the proposed fix, which observation best proves the requirement was met?
- A recipient receives only the permitted status information
- All calling flows consume the same tested approval result
- Subsequent runs act only on new eligible records
- The test message appears in expected mail logs and arrives without rejected delivery for both old and new incoming workflow emails records
Explanation
Correct Answer
C:Subsequent runs act only on new eligible records. This verifies the effect of filter by status and a durable last-processed or eligibility criterion.
Incorrect Answers
A:This test would assess another concern: In the scoped Notification Center app handling case email messages, a notification template includes confidential investigation notes visible to an external recipient. It does not verify the stated 4.2 requirement.
B:This test would assess another concern: In the scoped Approval Automation app handling request lifecycle, a team needs reusable approval processing in five flows but duplicates the same sequence in each. It does not verify the stated 4.2 requirement.
D: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.2 requirement.
Question 819
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Measure job duration and alert on unexpected volume
- Test approval and rejection using separate execution traces and keep a rollback plan for the Task Automation release
- Test updates that change other fields and repeat saves
- Check draft/published state during release testing
Explanation
Correct Answer
A:Measure job duration and alert on unexpected volume. It prevents the following recurring problem: Scheduled jobs should query only eligible records and track processing state.
Incorrect Answers
B:That safeguard addresses a different application case: During a change review of the scoped Task Automation app used for automated approvals, a conditional flow must stop on rejected approval but sends fulfillment tasks anyway. Previously created automated approvals 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 Approval Automation app handling request lifecycle, a flow should start when an approval request changes to Ready but runs on unrelated edits. It does not control the cause here.
D:That safeguard addresses a different application case: 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. It does not control the cause here.
Question 820
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. Select THREE complementary measures or outcomes that address this case.
- Filter by status and a durable last-processed or eligibility criterion
- Turn off logging to reduce database load
- Subsequent runs act only on new eligible records
- Reset processed flags on every run
- Measure job duration and alert on unexpected volume
- Run a query without conditions each hour
Explanation
Correct Answers
A:Filter by status and a durable last-processed or eligibility criterion. The diagnosed cause is: Scheduled jobs should query only eligible records and track processing state.
C:Filter by status and a durable last-processed or eligibility criterion. This is the direct observed result required before acceptance.
E:Measure job duration and alert on unexpected volume. It guards against the recurring issue: Scheduled jobs should query only eligible records and track processing state.
Incorrect Answers
B:“Turn off logging to reduce database load” would leave this failure unresolved: Scheduled jobs should query only eligible records and track processing state.
D:“Reset processed flags on every run” would leave this failure unresolved: Scheduled jobs should query only eligible records and track processing state.
F:“Run a query without conditions each hour” would leave this failure unresolved: Scheduled jobs should query only eligible records and track processing state.
ServiceNow Certified Application Developer (CAD) Practice Tests