100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 390
In the scoped Lab Reservations app handling instrument bookings, a contractor's delegated development access remains enabled after the delivery engagement ends. Select THREE complementary measures or outcomes that address this case.
- Review delegated access after contract and personnel changes
- The former contractor cannot modify app files or protected resources
- Rename the contractor display name to revoke access
- Leave access indefinitely as a convenience
- Rely on lack of navigation visibility as revocation
- Remove the contractor's delegated developer assignment when the approved work ends
Explanation
Correct Answers
A:Review delegated access after contract and personnel changes. It guards against the recurring issue: Time-bounded delegation requires revocation and least privilege.
B:Remove the contractor's delegated developer assignment when the approved work ends. This is the direct observed result required before acceptance.
F:Remove the contractor's delegated developer assignment when the approved work ends. The diagnosed cause is: Time-bounded delegation requires revocation and least privilege.
Incorrect Answers
C:“Rename the contractor display name to revoke access” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
D:“Leave access indefinitely as a convenience” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
E:“Rely on lack of navigation visibility as revocation” would leave this failure unresolved: Time-bounded delegation requires revocation and least privilege.
Question 391
During a change review of the scoped Employee Moves app used for employment requests, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. Previously created employment requests records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Make the name field longer without checking existing employment requests data
- Match users by their screen name alone without checking existing employment requests data
- Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records
- Copy the user profile into every text field without checking existing employment requests data
Explanation
Correct Answer
C:Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records. The reason is that a string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
Incorrect Answers
A:“Make the name field longer without checking existing employment requests data” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
B:“Match users by their screen name alone without checking existing employment requests data” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
D:“Copy the user profile into every text field without checking existing employment requests data” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
Question 392
During a change review of the scoped Employee Moves app used for employment requests, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. Previously created employment requests records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file; existing new project approvals also require backward-compatible behavior
- A viable app must account for data classification, ownership and retention, not only screen creation
- A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior
- The navigation target is an independent application configuration that must match the intended artifact; existing visitor authorizations also require backward-compatible behavior
Explanation
Correct Answer
C:Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records. The underlying issue is that a string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Project Intake app used for new project approvals, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. Previously created new project approvals 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 Training Enrollment app handling course requests, a proposed app stores confidential investigations in generic notes with no retention or responsible team. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Site Visits app used for visitor authorizations, a menu module opens the wrong table because its link target was copied from another app. Previously created visitor authorizations records must remain valid after the change. It does not explain the failure here.
Question 393
During a change review of the scoped Employee Moves app used for employment requests, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. Previously created employment requests records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- A changed display name resolves consistently without rewriting each request for both old and new employment requests records
- Authorized staff can navigate to the expected list from the application menu for both old and new document workflows records
- Two separately installed apps work without replacing each other's helpers for both old and new retirement requests records
- Direct-link attempts by unauthorized users fail to retrieve protected data for both old and new course requests records
Explanation
Correct Answer
A:A changed display name resolves consistently without rewriting each request for both old and new employment requests records. This verifies the effect of use an appropriate reference field to the authorized user record and regression-test the existing employment requests records.
Incorrect Answers
B:This test would assess another concern: During a change review of the scoped Document Requests app used for document workflows, a scoped application exists but staff cannot find its list in the All navigation menu. Previously created document workflows records must remain valid after the change. It does not verify the stated 1.2 requirement.
C:This test would assess another concern: During a change review of the scoped Asset Disposal app used for retirement requests, a scoped application contains utility scripts with generic globally conflicting names. Previously created retirement requests records must remain valid after the change. It does not verify the stated 1.2 requirement.
D:This test would assess another concern: During a change review of the scoped Training Enrollment app used for course requests, a requester can guess an admin module URL despite the module being hidden from the menu. Previously created course requests records must remain valid after the change. It does not verify the stated 1.2 requirement.
Question 394
During a change review of the scoped Employee Moves app used for employment requests, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. Previously created employment requests records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test both navigation visibility and direct access under non-admin roles and keep a rollback plan for the Training Enrollment release
- Maintain a requirement-to-capability map before creating custom tables and keep a rollback plan for the Vendor Onboarding release
- Test reference targets and ACLs against non-admin personas and keep a rollback plan for the Employee Moves release
- Test each CRUD operation separately between scopes and keep a rollback plan for the Security Exceptions release
Explanation
Correct Answer
C:Test reference targets and ACLs against non-admin personas and keep a rollback plan for the Employee Moves release. It prevents the following recurring problem: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Training Enrollment app used for course requests, a requester can guess an admin module URL despite the module being hidden from the menu. Previously created course requests 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 Vendor Onboarding app used for supplier qualification, a developer plans to recreate an existing standard task-management feature as a custom app without checking existing capabilities. Previously created supplier qualification records must remain valid after the change. It does not control the cause here.
D:That safeguard addresses a different application case: During a change review of the scoped Security Exceptions app used for risk acknowledgments, an app consumes another scoped table and mistakenly assumes the target table's read settings imply permission to write. Previously created risk acknowledgments records must remain valid after the change. It does not control the cause here.
Question 395
During a change review of the scoped Employee Moves app used for employment requests, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. Previously created employment requests records must remain valid after the change. Select TWO complementary measures or outcomes that address this case.
- Copy the user profile into every text field without checking existing employment requests data
- Match users by their screen name alone without checking existing employment requests data
- Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records
- A changed display name resolves consistently without rewriting each request for both old and new employment requests records
- Make the name field longer without checking existing employment requests data
Explanation
Correct Answers
C:Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records. The diagnosed cause is: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
D:Use an appropriate reference field to the authorized user record and regression-test the existing employment requests records. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Copy the user profile into every text field without checking existing employment requests data” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
B:“Match users by their screen name alone without checking existing employment requests data” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
E:“Make the name field longer without checking existing employment requests data” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record; existing employment requests also require backward-compatible behavior.
Question 396
During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. What is the most appropriate supported design or corrective action?
- Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records
- Add an after Business Rule solely to change browser appearance without checking existing building-entry requests data
- Require the field for every request type without checking existing building-entry requests data
- Use an ACL as a form-required indicator without checking existing building-entry requests data
Explanation
Correct Answer
A:Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records. The reason is that a declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
B:“Add an after Business Rule solely to change browser appearance without checking existing building-entry requests data” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
C:“Require the field for every request type without checking existing building-entry requests data” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
D:“Use an ACL as a form-required indicator without checking existing building-entry requests data” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
Question 397
During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. Which explanation best identifies the underlying ServiceNow application-development problem?
- Duplicate processing and retries need an explicit idempotent submission boundary
- UI Policies and Client Scripts are not authoritative server-side data-integrity enforcement; existing partner record synchronization also require backward-compatible behavior
- A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior
- Multiple UI-specific defaults can disagree with server-side record creation paths
Explanation
Correct Answer
C:Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records. The underlying issue is that a declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app case: 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. It does not explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Integration Reviews app used for partner record synchronization, a read-only form field is submitted through a REST API with a changed value that bypasses UI rules. Previously created partner record synchronization 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 Quality Inspections app handling inspection cases, a developer needs a default value for a classification field but hard-codes it in several form scripts. It does not explain the failure here.
Question 398
During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. After the proposed fix, which observation best proves the requirement was met?
- Authorized staff see only the related records for the current parent
- Changing Emergency on and off updates the required field consistently for both old and new building-entry requests records
- Authorized staff see only the related records for the current parent for both old and new planned outages records
- A submitted sample has the expected date on the created record
Explanation
Correct Answer
B:Changing Emergency on and off updates the required field consistently for both old and new building-entry requests records. This verifies the effect of configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records.
Incorrect Answers
A:This test would assess another concern: In the scoped Office Relocation app handling move requests, a staff form omits a related list needed to inspect the child's requests. It does not verify the stated 2.2 requirement.
C:This test would assess another concern: During a change review of the scoped Maintenance Windows app used for planned outages, a staff form omits a related list needed to inspect the child's requests. Previously created planned outages records must remain valid after the change. It does not verify the stated 2.2 requirement.
D:This test would assess another concern: In the scoped Service Request Intake app handling portal submissions, a Record Producer collects a contact date but the created record has a blank corresponding field. It does not verify the stated 2.2 requirement.
Question 399
During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test policy reverse behavior and conflict with existing client scripts and keep a rollback plan for the Facilities Access release
- Test trigger timing and null handling for each Business Rule operation and keep a rollback plan for the Office Relocation release
- Test bypass attempts and non-high-risk requests
- Verify related-list access uses the underlying ACL permissions
Explanation
Correct Answer
A:Test policy reverse behavior and conflict with existing client scripts and keep a rollback plan for the Facilities Access release. It prevents the following recurring problem: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
B:That safeguard addresses a different application case: During a change review of the scoped Office Relocation app used for move requests, a script compares current.priority and previous.priority but runs on insert when previous is unavailable. Previously created move 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 Service Request Intake app handling portal submissions, a service-catalog producer requires a justification only for high-risk request categories. It does not control the cause here.
D:That safeguard addresses a different application case: In the scoped Office Relocation app handling move requests, a staff form omits a related list needed to inspect the child's requests. It does not control the cause here.
Question 400
During a change review of the scoped Facilities Access app used for building-entry requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Previously created building-entry requests records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Changing Emergency on and off updates the required field consistently for both old and new building-entry requests records
- Test policy reverse behavior and conflict with existing client scripts and keep a rollback plan for the Facilities Access release
- Use an ACL as a form-required indicator without checking existing building-entry requests data
- Require the field for every request type without checking existing building-entry requests data
- Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records
- Add an after Business Rule solely to change browser appearance without checking existing building-entry requests data
Explanation
Correct Answers
A:Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records. This is the direct observed result required before acceptance.
B:Test policy reverse behavior and conflict with existing client scripts and keep a rollback plan for the Facilities Access release. It guards against the recurring issue: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
E:Configure a UI Policy with a condition and mandatory field action and regression-test the existing building-entry requests records. The diagnosed cause is: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
Incorrect Answers
C:“Use an ACL as a form-required indicator without checking existing building-entry requests data” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
D:“Require the field for every request type without checking existing building-entry requests data” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
F:“Add an after Business Rule solely to change browser appearance without checking existing building-entry requests data” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script; existing building-entry requests also require backward-compatible behavior.
ServiceNow Certified Application Developer (CAD) Practice Tests