100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 370
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Select THREE complementary measures or outcomes that address this case.
- Test policy reverse behavior and conflict with existing client scripts
- Add an after Business Rule solely to change browser appearance
- Changing Emergency on and off updates the required field consistently
- Require the field for every request type
- Configure a UI Policy with a condition and mandatory field action
- Use an ACL as a form-required indicator
Explanation
Correct Answers
A:Test policy reverse behavior and conflict with existing client scripts. It guards against the recurring issue: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
C:Configure a UI Policy with a condition and mandatory field action. This is the direct observed result required before acceptance.
E:Configure a UI Policy with a condition and mandatory field action. The diagnosed cause is: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Incorrect Answers
B:“Add an after Business Rule solely to change browser appearance” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
D:“Require the field for every request type” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
F:“Use an ACL as a form-required indicator” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Question 371
In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. What is the most appropriate supported design or corrective action?
- Use a UI Policy as a role grant
- Hard-code the employee sys_id into the ACL
- Disable the table ACL to make the problem disappear
- Verify effective membership and required role grants before modifying ACL policy
Explanation
Correct Answer
D:Verify effective membership and required role grants before modifying ACL policy. The reason is that role assignment and group membership must be evaluated for the actual logged-in user.
Incorrect Answers
A:“Use a UI Policy as a role grant” would leave the failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
B:“Hard-code the employee sys_id into the ACL” would leave the failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
C:“Disable the table ACL to make the problem disappear” would leave the failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
Question 372
In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. Which explanation best identifies the underlying ServiceNow application-development problem?
- Role assignment and group membership must be evaluated for the actual logged-in user
- ACL decisions require the complete role, condition and script logic to be evaluated correctly; existing protected case records also require backward-compatible behavior
- Blanket privilege expansion increases accidental access and maintenance risk; existing relocation checklists also require backward-compatible behavior
- Cross-scope reachability does not replace proper service account roles and endpoint authorization
Explanation
Correct Answer
A:Verify effective membership and required role grants before modifying ACL policy. The underlying issue is that role assignment and group membership must be evaluated for the actual logged-in user.
Incorrect Answers
B:This explanation belongs to another app case: 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 explain the failure here.
C:This explanation belongs to another app case: 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 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 373
In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. After the proposed fix, which observation best proves the requirement was met?
- The employee receives intended access after proper role provisioning
- Users holding only one privilege are denied the protected action for both old and new protected case records records
- The one required lookup works while unrelated operations are still denied
- Only authorized scopes can attach new server logic to the protected table
Explanation
Correct Answer
A:The employee receives intended access after proper role provisioning. This verifies the effect of verify effective membership and required role grants before modifying ACL policy.
Incorrect Answers
B:This test would assess another concern: During a change review of the scoped Security Exceptions app used for protected case records, an ACL allows access when the user has one of two roles but the policy requires both approval and finance privileges. Previously created protected case records records must remain valid after the change. It does not verify the stated 3.1 requirement.
C: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.
D:This test would assess another concern: In the scoped Visitor Badging app handling temporary credentials, a scoped app creates a Business Rule on another app's table without approved application access. It does not verify the stated 3.1 requirement.
Question 374
In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. 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
- Audit API exposure and operation-specific ACLs and keep a rollback plan for the Asset Disposal release
- Inspect helper input, output fields and caller ACLs during review
- Include role-provisioning diagnostics in onboarding tests
Explanation
Correct Answer
D:Include role-provisioning diagnostics in onboarding tests. It prevents the following recurring problem: Role assignment and group membership must be evaluated for the actual logged-in user.
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: 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 control the cause here.
C:That safeguard addresses a different application case: 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 control the cause here.
Question 375
In the scoped Employee Services app handling staff records, a role is granted to a group but a newly added employee still cannot see the protected application. Select TWO complementary measures or outcomes that address this case.
- Use a UI Policy as a role grant
- Hard-code the employee sys_id into the ACL
- The employee receives intended access after proper role provisioning
- Verify effective membership and required role grants before modifying ACL policy
- Disable the table ACL to make the problem disappear
Explanation
Correct Answers
C:Verify effective membership and required role grants before modifying ACL policy. This is the direct observed result required before acceptance.
D:Verify effective membership and required role grants before modifying ACL policy. The diagnosed cause is: Role assignment and group membership must be evaluated for the actual logged-in user.
Incorrect Answers
A:“Use a UI Policy as a role grant” would leave this failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
B:“Hard-code the employee sys_id into the ACL” would leave this failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
E:“Disable the table ACL to make the problem disappear” would leave this failure unresolved: Role assignment and group membership must be evaluated for the actual logged-in user.
Question 376
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. What is the most appropriate supported design or corrective action?
- Define the subflow output and assign it before completion
- Turn the result into a static annotation
- Assume every local variable becomes an output automatically
- Put the result in an invisible form field only
Explanation
Correct Answer
A:Define the subflow output and assign it before completion. The reason is that reusable subflows need declared inputs and outputs for data exchange.
Incorrect Answers
B:“Turn the result into a static annotation” would leave the failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
C:“Assume every local variable becomes an output automatically” would leave the failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
D:“Put the result in an invisible form field only” would leave the failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
Question 377
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. Which explanation best identifies the underlying ServiceNow application-development problem?
- Browser events are not suitable for unattended scheduled server operations
- Notification timing must match the persisted and approved business state
- Reusable subflows need declared inputs and outputs for data exchange
- Server utilities must validate parameters and enforce intended table and operation boundaries; existing repair requests also require backward-compatible behavior
Explanation
Correct Answer
C:Define the subflow output and assign it before completion. The underlying issue is that reusable subflows need declared inputs and outputs for data exchange.
Incorrect Answers
A:This explanation belongs to another app case: 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 explain the failure here.
B:This explanation belongs to another app case: In the scoped Approval Automation app handling request lifecycle, a workflow sends a status update before the database transaction commits and recipients see stale details. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Facilities Repairs app used for repair requests, a shared utility Script Include accepts an arbitrary target table from user-supplied input and updates records. Previously created repair requests records must remain valid after the change. It does not explain the failure here.
Question 378
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. After the proposed fix, which observation best proves the requirement was met?
- A rejection generates one outbound message with the correct content
- A reply adds information to the correct existing case without duplicates for both old and new incoming workflow emails records
- The calling flow receives the expected decision data pill
- Valid messages create an intended record, while unknown senders do not for both old and new incoming workflow emails records
Explanation
Correct Answer
C:The calling flow receives the expected decision data pill. This verifies the effect of define the subflow output and assign it before completion.
Incorrect Answers
A: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.
B:This test would assess another concern: During a change review of the scoped Correspondence Intake app used for incoming workflow emails, an inbound email replies to an existing case but the system creates a duplicate instead of correlating 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: 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 verify the stated 4.1 requirement.
Question 379
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Unit-test the helper and enforce scoped caller permissions and keep a rollback plan for the Grant Applications release
- Contract-test the subflow against all calling flows
- Perform template field and recipient privacy review
- Set a safe default and restrict who can modify the property
Explanation
Correct Answer
B:Contract-test the subflow against all calling flows. It prevents the following recurring problem: Reusable subflows need declared inputs and outputs for data exchange.
Incorrect Answers
A: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.
C:That safeguard addresses a different application case: 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 control the cause here.
D: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 380
In the scoped Approval Automation app handling request lifecycle, a subflow receives a record sys_id but a calling flow cannot use its calculated decision afterward. Select THREE complementary measures or outcomes that address this case.
- Turn the result into a static annotation
- Contract-test the subflow against all calling flows
- Define the subflow output and assign it before completion
- Put the result in an invisible form field only
- Assume every local variable becomes an output automatically
- The calling flow receives the expected decision data pill
Explanation
Correct Answers
B:Contract-test the subflow against all calling flows. It guards against the recurring issue: Reusable subflows need declared inputs and outputs for data exchange.
C:Define the subflow output and assign it before completion. The diagnosed cause is: Reusable subflows need declared inputs and outputs for data exchange.
F:Define the subflow output and assign it before completion. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Turn the result into a static annotation” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
D:“Put the result in an invisible form field only” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
E:“Assume every local variable becomes an output automatically” would leave this failure unresolved: Reusable subflows need declared inputs and outputs for data exchange.
ServiceNow Certified Application Developer (CAD) Practice Tests