100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 980
In the scoped Notification Center app handling case email messages, a notification template includes confidential investigation notes visible to an external recipient. Select THREE complementary measures or outcomes that address this case.
- Embed the full record JSON in the email
- Trust email subject confidentiality
- A recipient receives only the permitted status information
- Perform template field and recipient privacy review
- Obfuscate restricted text with HTML color
- Remove restricted fields from the template and use an approved minimal message
Explanation
Correct Answers
C:Remove restricted fields from the template and use an approved minimal message. This is the direct observed result required before acceptance.
D:Perform template field and recipient privacy review. It guards against the recurring issue: Email content generation must respect data classification and recipient authorization.
F:Remove restricted fields from the template and use an approved minimal message. The diagnosed cause is: Email content generation must respect data classification and recipient authorization.
Incorrect Answers
A:“Embed the full record JSON in the email” would leave this failure unresolved: Email content generation must respect data classification and recipient authorization.
B:“Trust email subject confidentiality” would leave this failure unresolved: Email content generation must respect data classification and recipient authorization.
E:“Obfuscate restricted text with HTML color” would leave this failure unresolved: Email content generation must respect data classification and recipient authorization.
Question 981
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. What is the most appropriate supported design or corrective action?
- Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records
- Delete the application namespace for a cosmetic rename without checking existing planned outages data
- Use a globally named Script Include for every private helper without checking existing planned outages data
- Edit every x_ prefix manually in deployed scripts without checking existing planned outages data
Explanation
Correct Answer
A:Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records. The reason is that display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Incorrect Answers
B:“Delete the application namespace for a cosmetic rename without checking existing planned outages data” would leave the failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
C:“Use a globally named Script Include for every private helper without checking existing planned outages data” would leave the failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
D:“Edit every x_ prefix manually in deployed scripts without checking existing planned outages data” would leave the failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Question 982
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- A string copy loses referential integrity and reliable linkage to the existing person record
- Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior
- Choosing platform fit includes reusing suitable supported features rather than duplicating them blindly; existing supplier qualification also require backward-compatible behavior
- 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
B:Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records. The underlying issue is that display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Employee Services app handling staff records, a new app stores an employee name as unstructured text on each request and cannot consistently reference the employee record. It does not explain the failure here.
C:This explanation belongs to another app 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 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 983
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. After the proposed fix, which observation best proves the requirement was met?
- The app can be relabeled without breaking scoped script references for both old and new planned outages records
- Authorized staff can navigate to the expected list from the application menu
- Role-based tests show submitters cannot approve their own protected records
- Delete and archive tests leave no unintended orphan references for both old and new policy waivers records
Explanation
Correct Answer
A:The app can be relabeled without breaking scoped script references for both old and new planned outages records. This verifies the effect of plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records.
Incorrect Answers
B:This test would assess another concern: 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 verify the stated 1.4 requirement.
C:This test would assess another concern: In the scoped Approval Automation app handling request lifecycle, a request workflow must be accessible to approvers and submitters, but the proposal gives everyone the admin role. It does not verify the stated 1.4 requirement.
D:This test would assess another concern: During a change review of the scoped Compliance Exceptions app used for policy waivers, deleting a parent application record unexpectedly leaves child audit records with broken references. Previously created policy waivers records must remain valid after the change. It does not verify the stated 1.4 requirement.
Question 984
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Review referential integrity and retention impacts before table lifecycle changes
- Test navigation role assignments and independently verify data ACLs
- Freeze scope/API naming early and review any migration needs separately and keep a rollback plan for the Maintenance Windows release
- Review menu title, module order and visibility with actual personas and keep a rollback plan for the Document Requests release
Explanation
Correct Answer
C:Freeze scope/API naming early and review any migration needs separately and keep a rollback plan for the Maintenance Windows release. It prevents the following recurring problem: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Employee Moves app handling relocation checklists, deleting a parent application record unexpectedly leaves child audit records with broken references. It does not control the cause here.
B: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.
D:That safeguard addresses a different application case: 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 control the cause here.
Question 985
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. Select TWO complementary measures or outcomes that address this case.
- Use a globally named Script Include for every private helper without checking existing planned outages data
- Delete the application namespace for a cosmetic rename without checking existing planned outages data
- The app can be relabeled without breaking scoped script references for both old and new planned outages records
- Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records
- Edit every x_ prefix manually in deployed scripts without checking existing planned outages data
Explanation
Correct Answers
C:Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records. This is the direct observed result required before acceptance.
D:Plan and preserve the approved application scope and API naming conventions and regression-test the existing planned outages records. The diagnosed cause is: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Incorrect Answers
A:“Use a globally named Script Include for every private helper without checking existing planned outages data” would leave this failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
B:“Delete the application namespace for a cosmetic rename without checking existing planned outages data” would leave this failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
E:“Edit every x_ prefix manually in deployed scripts without checking existing planned outages data” would leave this failure unresolved: Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior.
Question 986
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. What is the most appropriate supported design or corrective action?
- Match the record by display text alone without checking existing inspection cases data
- Move confidential query logic to public client code without checking existing inspection cases data
- Run query() without any filters without checking existing inspection cases data
- Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records
Explanation
Correct Answer
D:Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records. The reason is that an unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
Incorrect Answers
A:“Match the record by display text alone without checking existing inspection cases data” would leave the failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
B:“Move confidential query logic to public client code without checking existing inspection cases data” would leave the failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
C:“Run query() without any filters without checking existing inspection cases data” would leave the failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
Question 987
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior
- Duplicate processing and retries need an explicit idempotent submission boundary
- Visual placement does not enforce sensitive field access controls; existing employment requests also require backward-compatible behavior
- Multiple UI-specific defaults can disagree with server-side record creation paths
Explanation
Correct Answer
A:Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records. The underlying issue is that an unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
Incorrect Answers
B: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.
C:This explanation belongs to another app case: During a change review of the scoped Employee Moves app used for employment requests, a form shows a confidential salary field to the wrong persona because it is placed on the default view. Previously created employment requests 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 988
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. After the proposed fix, which observation best proves the requirement was met?
- The form receives only the quota decision without leaking restricted rows
- Retrying the same submission produces one logical record
- Execution retrieves the intended record without scanning unrelated rows for both old and new inspection cases records
- The form consistently applies the same visible and mandatory rules across conditions for both old and new relocation checklists records
Explanation
Correct Answer
C:Execution retrieves the intended record without scanning unrelated rows for both old and new inspection cases records. This verifies the effect of use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records.
Incorrect Answers
A:This test would assess another concern: In the scoped Application Audits app handling review evidence, a developer tries to call GlideRecord directly from a browser script to check a confidential quota. It does not verify the stated 2.3 requirement.
B:This test would assess another concern: 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 verify the stated 2.3 requirement.
D:This test would assess another concern: During a change review of the scoped Employee Moves app used for relocation checklists, a UI Policy conflicts with a Client Script over the same field's visibility and behaves unexpectedly. Previously created relocation checklists records must remain valid after the change. It does not verify the stated 2.3 requirement.
Question 989
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test onLoad and onChange paths with performance instrumentation
- Test reference ambiguity and permissions in producer submissions
- Review query cardinality and server-side ACL expectations and keep a rollback plan for the Quality Inspections release
- Review form-view changes with each intended user role
Explanation
Correct Answer
C:Review query cardinality and server-side ACL expectations and keep a rollback plan for the Quality Inspections release. It prevents the following recurring problem: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Vendor Onboarding app handling supplier qualification, an onChange Client Script performs an expensive lookup every time the form initially loads. 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: 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 control the cause here.
Question 990
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. Select THREE complementary measures or outcomes that address this case.
- Run query() without any filters without checking existing inspection cases data
- Review query cardinality and server-side ACL expectations and keep a rollback plan for the Quality Inspections release
- Execution retrieves the intended record without scanning unrelated rows for both old and new inspection cases records
- Match the record by display text alone without checking existing inspection cases data
- Move confidential query logic to public client code without checking existing inspection cases data
- Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records
Explanation
Correct Answers
B:Review query cardinality and server-side ACL expectations and keep a rollback plan for the Quality Inspections release. It guards against the recurring issue: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
C:Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records. This is the direct observed result required before acceptance.
F:Use a constrained GlideRecord query or get by known valid key with permission awareness and regression-test the existing inspection cases records. The diagnosed cause is: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
Incorrect Answers
A:“Run query() without any filters without checking existing inspection cases data” would leave this failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
D:“Match the record by display text alone without checking existing inspection cases data” would leave this failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
E:“Move confidential query logic to public client code without checking existing inspection cases data” would leave this failure unresolved: An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior.
ServiceNow Certified Application Developer (CAD) Practice Tests