100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 670
In the scoped License Renewals app handling entitlement reviews, a Client Script checks the user's role to hide a sensitive form section. Select THREE complementary measures or outcomes that address this case.
- Encode the secret in a hidden HTML element
- Include non-admin API tests in security acceptance criteria
- Rely on g_user.hasRole alone
- Assume a masked input controls data reads
- Use client logic for usability and enforce the permission with table and field ACLs
- Unauthorized API and list requests also cannot read the protected values
Explanation
Correct Answers
B:Include non-admin API tests in security acceptance criteria. It guards against the recurring issue: Client-side role checks improve presentation but cannot protect data from non-UI access.
E:Use client logic for usability and enforce the permission with table and field ACLs. The diagnosed cause is: Client-side role checks improve presentation but cannot protect data from non-UI access.
F:Use client logic for usability and enforce the permission with table and field ACLs. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Encode the secret in a hidden HTML element” would leave this failure unresolved: Client-side role checks improve presentation but cannot protect data from non-UI access.
C:“Rely on g_user.hasRole alone” would leave this failure unresolved: Client-side role checks improve presentation but cannot protect data from non-UI access.
D:“Assume a masked input controls data reads” would leave this failure unresolved: Client-side role checks improve presentation but cannot protect data from non-UI access.
Question 671
In the scoped Access Governance app handling permission reviews, a scripted ACL compares a user's visible full name text as its only authorization identity. What is the most appropriate supported design or corrective action?
- Authorize by an email subject
- Use stable user identity or role ownership checks in the ACL condition
- Compare localized full name strings
- Grant public access when a display name changes
Explanation
Correct Answer
B:Use stable user identity or role ownership checks in the ACL condition. The reason is that display names are mutable and insufficient as a robust authorization boundary.
Incorrect Answers
A:“Authorize by an email subject” would leave the failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
C:“Compare localized full name strings” would leave the failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
D:“Grant public access when a display name changes” would leave the failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
Question 672
In the scoped Access Governance app handling permission reviews, a scripted ACL compares a user's visible full name text as its only authorization identity. Which explanation best identifies the underlying ServiceNow application-development problem?
- Cross-scope reachability does not replace proper service account roles and endpoint authorization
- Scope isolation alone does not guarantee correctly configured record-level ACLs; existing vendor assessments also require backward-compatible behavior
- Display names are mutable and insufficient as a robust authorization boundary
- Creating application files on foreign tables is controlled by application-access settings
Explanation
Correct Answer
C:Use stable user identity or role ownership checks in the ACL condition. The underlying issue is that display names are mutable and insufficient as a robust authorization boundary.
Incorrect Answers
A: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.
B:This explanation belongs to another app case: During a change review of the scoped Supplier Reviews app used for vendor assessments, a sensitive table is copied into a new scope with default permissive access settings. Previously created vendor assessments 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 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 explain the failure here.
Question 673
In the scoped Access Governance app handling permission reviews, a scripted ACL compares a user's visible full name text as its only authorization identity. After the proposed fix, which observation best proves the requirement was met?
- The manager can view records but deletion is blocked without the privileged role
- The worker edits notes but a direct update to decision is denied for both old and new temporary credentials records
- The approved source scope calls the resource while unknown scopes remain blocked for both old and new building-entry requests records
- Renaming a user does not change who can access the record
Explanation
Correct Answer
D:Renaming a user does not change who can access the record. This verifies the effect of use stable user identity or role ownership checks in the ACL condition.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 3.2 requirement.
B:This test would assess another concern: During a change review of the scoped Visitor Badging app used for temporary credentials, a case worker may edit notes but should not change the protected approval decision. Previously created temporary credentials records must remain valid after the change. It does not verify the stated 3.2 requirement.
C:This test would assess another concern: 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 verify the stated 3.2 requirement.
Question 674
In the scoped Access Governance app handling permission reviews, a scripted ACL compares a user's visible full name text as its only authorization identity. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Include row-level unauthorized access tests
- Revisit cross-scope grants when consumers or application versions change
- Run non-UI create attempts in acceptance testing and keep a rollback plan for the Task Automation release
- Test identity changes and role revocations
Explanation
Correct Answer
D:Test identity changes and role revocations. It prevents the following recurring problem: Display names are mutable and insufficient as a robust authorization boundary.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Security Exceptions app handling risk acknowledgments, a requester should see only their own application records, not all records in the table. It does not control the cause here.
B:That safeguard addresses a different application case: 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. It does not control the cause here.
C:That safeguard addresses a different application case: 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 control the cause here.
Question 675
In the scoped Access Governance app handling permission reviews, a scripted ACL compares a user's visible full name text as its only authorization identity. Select TWO complementary measures or outcomes that address this case.
- Grant public access when a display name changes
- Renaming a user does not change who can access the record
- Authorize by an email subject
- Compare localized full name strings
- Use stable user identity or role ownership checks in the ACL condition
Explanation
Correct Answers
B:Use stable user identity or role ownership checks in the ACL condition. This is the direct observed result required before acceptance.
E:Use stable user identity or role ownership checks in the ACL condition. The diagnosed cause is: Display names are mutable and insufficient as a robust authorization boundary.
Incorrect Answers
A:“Grant public access when a display name changes” would leave this failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
C:“Authorize by an email subject” would leave this failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
D:“Compare localized full name strings” would leave this failure unresolved: Display names are mutable and insufficient as a robust authorization boundary.
Question 676
In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. What is the most appropriate supported design or corrective action?
- Change the text of the sender signature only
- Create an unrelated scheduled job
- Send all records to the event queue on every update
- Register and emit the intended event name using the approved event mechanism
Explanation
Correct Answer
D:Register and emit the intended event name using the approved event mechanism. The reason is that registered event names and their consumers must match exactly.
Incorrect Answers
A:“Change the text of the sender signature only” would leave the failure unresolved: Registered event names and their consumers must match exactly.
B:“Create an unrelated scheduled job” would leave the failure unresolved: Registered event names and their consumers must match exactly.
C:“Send all records to the event queue on every update” would leave the failure unresolved: Registered event names and their consumers must match exactly.
Question 677
In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. 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
- Registered event names and their consumers must match exactly
- Two independently configured notification paths can duplicate messages
- Inbound actions need validated sender and payload handling before record mutation; existing incoming workflow emails also require backward-compatible behavior
Explanation
Correct Answer
B:Register and emit the intended event name using the approved event mechanism. The underlying issue is that registered event names and their consumers must match exactly.
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.
C: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.
D: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.
Question 678
In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. After the proposed fix, which observation best proves the requirement was met?
- Only approved transitions send the expected message to the requester
- A rejection generates one outbound message with the correct content
- The event log and notification trace show the intended named event
- The outgoing email reaches the intended requester in a test
Explanation
Correct Answer
C:The event log and notification trace show the intended named event. This verifies the effect of register and emit the intended event name using the approved event mechanism.
Incorrect Answers
A:This test would assess another concern: In the scoped Maintenance Windows app handling planned outages, an app must notify a requester only after the approval outcome becomes Approved. It does not verify the stated 4.2 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.2 requirement.
D:This test would assess another concern: 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 verify the stated 4.2 requirement.
Question 679
In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test all branch outcomes and action input contracts and keep a rollback plan for the Facilities Access release
- Add deliverability monitoring and clear failure logging
- Validate event registry entries and tests during application deployment
- Add deliverability monitoring and clear failure logging and keep a rollback plan for the Correspondence Intake release
Explanation
Correct Answer
C:Validate event registry entries and tests during application deployment. It prevents the following recurring problem: Registered event names and their consumers must match exactly.
Incorrect Answers
A:That safeguard addresses a different application 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 control the cause here.
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.
D:That safeguard addresses a different application case: 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 control the cause here.
Question 680
In the scoped Notification Center app handling case email messages, a script triggers an event but no notification occurs because the event name is misspelled. Select THREE complementary measures or outcomes that address this case.
- Create an unrelated scheduled job
- Send all records to the event queue on every update
- The event log and notification trace show the intended named event
- Validate event registry entries and tests during application deployment
- Change the text of the sender signature only
- Register and emit the intended event name using the approved event mechanism
Explanation
Correct Answers
C:Register and emit the intended event name using the approved event mechanism. This is the direct observed result required before acceptance.
D:Validate event registry entries and tests during application deployment. It guards against the recurring issue: Registered event names and their consumers must match exactly.
F:Register and emit the intended event name using the approved event mechanism. The diagnosed cause is: Registered event names and their consumers must match exactly.
Incorrect Answers
A:“Create an unrelated scheduled job” would leave this failure unresolved: Registered event names and their consumers must match exactly.
B:“Send all records to the event queue on every update” would leave this failure unresolved: Registered event names and their consumers must match exactly.
E:“Change the text of the sender signature only” would leave this failure unresolved: Registered event names and their consumers must match exactly.
ServiceNow Certified Application Developer (CAD) Practice Tests