100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 720
During a change review of the scoped Maintenance Windows app used for planned outages, two contributors independently change the same Script Include and one silently overwrites the other's work. Previously created planned outages records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Resolve code conflicts by deleting all validation without checking existing planned outages data
- Both intended behaviors survive in the final reviewed source revision for both old and new planned outages records
- Review conflicting revisions and reconcile changes before committing the tested result and regression-test the existing planned outages records
- Use pull/compare and code-review controls for shared files and keep a rollback plan for the Maintenance Windows release
- Disable revision history without checking existing planned outages data
- Always choose the newest file regardless of tests without checking existing planned outages data
Explanation
Correct Answers
B:Review conflicting revisions and reconcile changes before committing the tested result and regression-test the existing planned outages records. This is the direct observed result required before acceptance.
C:Review conflicting revisions and reconcile changes before committing the tested result and regression-test the existing planned outages records. The diagnosed cause is: Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior.
D:Use pull/compare and code-review controls for shared files and keep a rollback plan for the Maintenance Windows release. It guards against the recurring issue: Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior.
Incorrect Answers
A:“Resolve code conflicts by deleting all validation without checking existing planned outages data” would leave this failure unresolved: Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior.
E:“Disable revision history without checking existing planned outages data” would leave this failure unresolved: Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior.
F:“Always choose the newest file regardless of tests without checking existing planned outages data” would leave this failure unresolved: Parallel source edits require change detection, merge review and conflict resolution; existing planned outages also require backward-compatible behavior.
Question 721
In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. What is the most appropriate supported design or corrective action?
- Specify and test dependent-record deletion, archival or restriction behavior according to policy
- Clear the displayed error message only
- Permit arbitrary deletion with no test
- Remove the parent identifier from all child forms
Explanation
Correct Answer
A:Specify and test dependent-record deletion, archival or restriction behavior according to policy. The reason is that relationship behavior and lifecycle policies were not designed before record deletion.
Incorrect Answers
B:“Clear the displayed error message only” would leave the failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
C:“Permit arbitrary deletion with no test” would leave the failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
D:“Remove the parent identifier from all child forms” would leave the failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
Question 722
In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. Which explanation best identifies the underlying ServiceNow application-development problem?
- Relationship behavior and lifecycle policies were not designed before record deletion
- A table alone does not establish a discoverable application module
- Navigation visibility should be scoped to the intended admin role
- A business-workflow platform should not be assumed to replace a dedicated high-rate telemetry processor; existing move requests also require backward-compatible behavior
Explanation
Correct Answer
A:Specify and test dependent-record deletion, archival or restriction behavior according to policy. The underlying issue is that relationship behavior and lifecycle policies were not designed before record deletion.
Incorrect Answers
B:This explanation belongs to another app case: In the scoped Incident Follow-ups app handling follow-up tasks, a scoped application exists but staff cannot find its list in the All navigation menu. It does not explain the failure here.
C:This explanation belongs to another app case: In the scoped Equipment Loans app handling borrowed assets, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Office Relocation app used for move requests, a team wants millisecond industrial sensor processing for millions of high-frequency samples and treats a custom Now Platform table as a streaming engine. Previously created move requests records must remain valid after the change. It does not explain the failure here.
Question 723
In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. After the proposed fix, which observation best proves the requirement was met?
- Only the approved application scope can invoke the protected resource for both old and new partner record synchronization records
- A clean install resolves expected scoped tables, roles and script references for both old and new movement requests records
- Performance tests show alerts arrive with the needed workflow context without ingesting raw streams
- Delete and archive tests leave no unintended orphan references
Explanation
Correct Answer
D:Delete and archive tests leave no unintended orphan references. This verifies the effect of specify and test dependent-record deletion, archival or restriction behavior according to policy.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Integration Reviews app used for partner record synchronization, a cross-scope resource should be called only by a known integration app, but all scopes are permitted. Previously created partner record synchronization records must remain valid after the change. It does not verify the stated 1.2 requirement.
B:This test would assess another concern: During a change review of the scoped Inventory Transfers app used for movement requests, a team starts a new scoped app without checking its name, scope and target instance and later must remap references. Previously created movement requests records must remain valid after the change. It does not verify the stated 1.2 requirement.
C:This test would assess another concern: In the scoped Document Requests app handling document workflows, a team wants millisecond industrial sensor processing for millions of high-frequency samples and treats a custom Now Platform table as a streaming engine. It does not verify the stated 1.2 requirement.
Question 724
In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Freeze scope/API naming early and review any migration needs separately and keep a rollback plan for the Maintenance Windows release
- Review referential integrity and retention impacts before table lifecycle changes
- Map the actual business handoff and exception paths before implementation
- Test navigation role assignments and independently verify data ACLs
Explanation
Correct Answer
B:Review referential integrity and retention impacts before table lifecycle changes. It prevents the following recurring problem: Relationship behavior and lifecycle policies were not designed before record deletion.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Maintenance Windows app used for planned outages, a developer renames a scoped application's display label and assumes its internal scope automatically changes. Previously created planned outages 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 Site Visits app handling visitor authorizations, an app proposal requires staff to see work assigned to their team across many handoffs and a shared status timeline. It does not control the cause here.
D:That safeguard addresses a different application case: In the scoped Equipment Loans app handling borrowed assets, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. It does not control the cause here.
Question 725
In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. Select TWO complementary measures or outcomes that address this case.
- Permit arbitrary deletion with no test
- Remove the parent identifier from all child forms
- Clear the displayed error message only
- Specify and test dependent-record deletion, archival or restriction behavior according to policy
- Delete and archive tests leave no unintended orphan references
Explanation
Correct Answers
D:Specify and test dependent-record deletion, archival or restriction behavior according to policy. The diagnosed cause is: Relationship behavior and lifecycle policies were not designed before record deletion.
E:Specify and test dependent-record deletion, archival or restriction behavior according to policy. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Permit arbitrary deletion with no test” would leave this failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
B:“Remove the parent identifier from all child forms” would leave this failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
C:“Clear the displayed error message only” would leave this failure unresolved: Relationship behavior and lifecycle policies were not designed before record deletion.
Question 726
In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. What is the most appropriate supported design or corrective action?
- Copy the field value into an unrelated hidden input
- Use supported GlideForm methods such as g_form.getValue for form fields
- Query document.getElementById for internal field markup
- Parse the field out of page HTML
Explanation
Correct Answer
B:Use supported GlideForm methods such as g_form.getValue for form fields. The reason is that direct DOM selectors are fragile across form layouts and platform updates.
Incorrect Answers
A:“Copy the field value into an unrelated hidden input” would leave the failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
C:“Query document.getElementById for internal field markup” would leave the failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
D:“Parse the field out of page HTML” would leave the failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
Question 727
In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. Which explanation best identifies the underlying ServiceNow application-development problem?
- Direct DOM selectors are fragile across form layouts and platform updates
- Multiple UI-specific defaults can disagree with server-side record creation paths
- An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior
- A form layout is a view of a record and can be tailored without changing underlying table storage
Explanation
Correct Answer
A:Use supported GlideForm methods such as g_form.getValue for form fields. The underlying issue is that direct DOM selectors are fragile across form layouts and platform updates.
Incorrect Answers
B: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.
C:This explanation belongs to another app case: During a change review of the scoped Quality Inspections app used for inspection cases, a server script queries all historical records and iterates them to find one known sys_id. Previously created inspection cases 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 Equipment Loans app handling borrowed assets, a case form shows a long serial-number field on an unrelated approval screen, confusing reviewers. It does not explain the failure here.
Question 728
In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. After the proposed fix, which observation best proves the requirement was met?
- The saved record includes the derived category without an extra self-update
- International users store consistent date values and reporting remains correct for both old and new course requests records
- The value is read consistently across tested supported form views
- Records created by form and automation receive consistent defaults for both old and new risk acknowledgments records
Explanation
Correct Answer
C:The value is read consistently across tested supported form views. This verifies the effect of use supported GlideForm methods such as g_form.getValue for form fields.
Incorrect Answers
A:This test would assess another concern: 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. It does not verify the stated 2.2 requirement.
B:This test would assess another concern: During a change review of the scoped Training Enrollment app used for course requests, a form uses a string field to collect a date and users enter ambiguous regional text. Previously created course requests records must remain valid after the change. It does not verify the stated 2.2 requirement.
D:This test would assess another concern: During a change review of the scoped Security Exceptions app used for risk acknowledgments, a developer needs a default value for a classification field but hard-codes it in several form scripts. Previously created risk acknowledgments records must remain valid after the change. It does not verify the stated 2.2 requirement.
Question 729
In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test trigger timing and null handling for each Business Rule operation
- Test reference ambiguity and permissions in producer submissions
- Avoid direct DOM manipulation for platform-managed controls
- Add negative API tests to acceptance criteria and keep a rollback plan for the Integration Reviews release
Explanation
Correct Answer
C:Avoid direct DOM manipulation for platform-managed controls. It prevents the following recurring problem: Direct DOM selectors are fragile across form layouts and platform updates.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Document Requests app handling document workflows, a script compares current.priority and previous.priority but runs on insert when previous is unavailable. It does not control the cause here.
B:That safeguard addresses a different application case: In the scoped Service Request Intake app handling portal submissions, a Record Producer populates a target reference using a typed display name and links the wrong record. It does not control the cause here.
D:That safeguard addresses a different application 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 control the cause here.
Question 730
In the scoped Fleet Maintenance app handling vehicle-service approvals, a browser script needs the current table field value but accesses an unsupported raw DOM selector. Select THREE complementary measures or outcomes that address this case.
- The value is read consistently across tested supported form views
- Parse the field out of page HTML
- Query document.getElementById for internal field markup
- Copy the field value into an unrelated hidden input
- Use supported GlideForm methods such as g_form.getValue for form fields
- Avoid direct DOM manipulation for platform-managed controls
Explanation
Correct Answers
A:Use supported GlideForm methods such as g_form.getValue for form fields. This is the direct observed result required before acceptance.
E:Use supported GlideForm methods such as g_form.getValue for form fields. The diagnosed cause is: Direct DOM selectors are fragile across form layouts and platform updates.
F:Avoid direct DOM manipulation for platform-managed controls. It guards against the recurring issue: Direct DOM selectors are fragile across form layouts and platform updates.
Incorrect Answers
B:“Parse the field out of page HTML” would leave this failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
C:“Query document.getElementById for internal field markup” would leave this failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
D:“Copy the field value into an unrelated hidden input” would leave this failure unresolved: Direct DOM selectors are fragile across form layouts and platform updates.
ServiceNow Certified Application Developer (CAD) Practice Tests