100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 540
During a change review of the scoped App Deployment app used for tested application releases, studio source-control link points at a different team's repository and imports unrelated application files. Previously created tested application releases records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Review repository permissions and configuration at onboarding and keep a rollback plan for the App Deployment release
- Verify repository URL, branch and application scope before importing or committing and regression-test the existing tested application releases records
- Remove application scope to resolve conflicts without checking existing tested application releases data
- Pull from the first similarly named repository without checking existing tested application releases data
- Disable commit history to avoid confusing names without checking existing tested application releases data
- The linked application files match the authorized repository and target branch for both old and new tested application releases records
Explanation
Correct Answers
A:Review repository permissions and configuration at onboarding and keep a rollback plan for the App Deployment release. It guards against the recurring issue: A source-control repository association must match the intended scoped application's ownership; existing tested application releases also require backward-compatible behavior.
B:Verify repository URL, branch and application scope before importing or committing and regression-test the existing tested application releases records. The diagnosed cause is: A source-control repository association must match the intended scoped application's ownership; existing tested application releases also require backward-compatible behavior.
F:Verify repository URL, branch and application scope before importing or committing and regression-test the existing tested application releases records. This is the direct observed result required before acceptance.
Incorrect Answers
C:“Remove application scope to resolve conflicts without checking existing tested application releases data” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership; existing tested application releases also require backward-compatible behavior.
D:“Pull from the first similarly named repository without checking existing tested application releases data” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership; existing tested application releases also require backward-compatible behavior.
E:“Disable commit history to avoid confusing names without checking existing tested application releases data” would leave this failure unresolved: A source-control repository association must match the intended scoped application's ownership; existing tested application releases also require backward-compatible behavior.
Question 541
In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. What is the most appropriate supported design or corrective action?
- Sort monetary text alphabetically
- Use a suitable numeric or currency field with specified units and validation
- Treat an empty string as a monetary zero without review
- Concatenate values in a Client Script for accounting totals
Explanation
Correct Answer
B:Use a suitable numeric or currency field with specified units and validation. The reason is that a textual field does not provide reliable numeric validation or aggregation.
Incorrect Answers
A:“Sort monetary text alphabetically” would leave the failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
C:“Treat an empty string as a monetary zero without review” would leave the failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
D:“Concatenate values in a Client Script for accounting totals” would leave the failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
Question 542
In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. Which explanation best identifies the underlying ServiceNow application-development problem?
- A viable app must account for data classification, ownership and retention, not only screen creation; existing repair requests also require backward-compatible behavior
- Navigation visibility should be scoped to the intended admin role; existing purchasing records also require backward-compatible behavior
- A good platform fit still requires role-specific access and least privilege
- A textual field does not provide reliable numeric validation or aggregation
Explanation
Correct Answer
D:Use a suitable numeric or currency field with specified units and validation. The underlying issue is that a textual field does not provide reliable numeric validation or aggregation.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Facilities Repairs app used for repair requests, a proposed app stores confidential investigations in generic notes with no retention or responsible team. Previously created repair requests records must remain valid after the change. It does not explain the failure here.
B:This explanation belongs to another app case: During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records 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 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 explain the failure here.
Question 543
In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. After the proposed fix, which observation best proves the requirement was met?
- Direct-link attempts by unauthorized users fail to retrieve protected data
- Opening the module lists only the intended records and retains correct scope context
- Reporting computes totals correctly and rejects malformed amounts
- Only the approved application scope can invoke the protected resource
Explanation
Correct Answer
C:Reporting computes totals correctly and rejects malformed amounts. This verifies the effect of use a suitable numeric or currency field with specified units and validation.
Incorrect Answers
A:This test would assess another concern: In the scoped Project Intake app handling new project approvals, a requester can guess an admin module URL despite the module being hidden from the menu. It does not verify the stated 1.2 requirement.
B:This test would assess another concern: In the scoped Grant Applications app handling grant reviews, a menu module opens the wrong table because its link target was copied from another app. It does not verify the stated 1.2 requirement.
D:This test would assess another concern: In the scoped Partner Integrations app handling external data exchange, a cross-scope resource should be called only by a known integration app, but all scopes are permitted. It does not verify the stated 1.2 requirement.
Question 544
In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Maintain a requirement-to-capability map before creating custom tables and keep a rollback plan for the Vendor Onboarding release
- Document process owners and the workflow boundary before building and keep a rollback plan for the Project Intake release
- Test navigation role assignments and independently verify data ACLs and keep a rollback plan for the Purchase Approvals release
- Use field type standards and sample-data tests during data-model review
Explanation
Correct Answer
D:Use field type standards and sample-data tests during data-model review. It prevents the following recurring problem: A textual field does not provide reliable numeric validation or aggregation.
Incorrect Answers
A: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.
B:That safeguard addresses a different application 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 control the cause here.
C:That safeguard addresses a different application case: During a change review of the scoped Purchase Approvals app used for purchasing records, an administrative configuration module appears to regular requestors even though it should be limited to app maintainers. Previously created purchasing records records must remain valid after the change. It does not control the cause here.
Question 545
In the scoped Asset Disposal app handling retirement requests, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. Select TWO complementary measures or outcomes that address this case.
- Reporting computes totals correctly and rejects malformed amounts
- Sort monetary text alphabetically
- Use a suitable numeric or currency field with specified units and validation
- Treat an empty string as a monetary zero without review
- Concatenate values in a Client Script for accounting totals
Explanation
Correct Answers
A:Use a suitable numeric or currency field with specified units and validation. This is the direct observed result required before acceptance.
C:Use a suitable numeric or currency field with specified units and validation. The diagnosed cause is: A textual field does not provide reliable numeric validation or aggregation.
Incorrect Answers
B:“Sort monetary text alphabetically” would leave this failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
D:“Treat an empty string as a monetary zero without review” would leave this failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
E:“Concatenate values in a Client Script for accounting totals” would leave this failure unresolved: A textual field does not provide reliable numeric validation or aggregation.
Question 546
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. What is the most appropriate supported design or corrective action?
- Send entire confidential table to the client
- Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax
- Store admin credentials inside the Client Script
- Grant broad read access so the browser query works
Explanation
Correct Answer
B:Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax. The reason is that browser-side record access is not a substitute for controlled server-side logic.
Incorrect Answers
A:“Send entire confidential table to the client” would leave the failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
C:“Store admin credentials inside the Client Script” would leave the failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
D:“Grant broad read access so the browser query works” would leave the failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
Question 547
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Field type and input controls affect data validation and consistent storage
- UI Policies and Client Scripts are not authoritative server-side data-integrity enforcement
- Browser-side record access is not a substitute for controlled server-side logic
- Unrestricted Business Rule conditions cause unnecessary actions and duplicates; existing policy exemptions also require backward-compatible behavior
Explanation
Correct Answer
C:Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax. The underlying issue is that browser-side record access is not a substitute for controlled server-side logic.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Project Intake app handling new project approvals, a form uses a string field to collect a date and users enter ambiguous regional text. It does not explain the failure here.
B:This explanation belongs to another app case: In the scoped Partner Integrations app handling external data exchange, a read-only form field is submitted through a REST API with a changed value that bypasses UI rules. It does not explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Training Waivers app used for policy exemptions, a Business Rule executes for every update even when the required status transition did not occur. Previously created policy exemptions records must remain valid after the change. It does not explain the failure here.
Question 548
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. After the proposed fix, which observation best proves the requirement was met?
- Execution retrieves the intended record without scanning unrelated rows for both old and new inspection cases records
- The form receives only the quota decision without leaking restricted rows
- Both UI and API invalid writes are rejected consistently
- One user update produces the expected final state without repeated executions for both old and new new project approvals records
Explanation
Correct Answer
B:The form receives only the quota decision without leaking restricted rows. This verifies the effect of expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax.
Incorrect Answers
A:This test would assess another concern: 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 verify the stated 2.2 requirement.
C:This test would assess another concern: In the scoped Partner Integrations app handling external data exchange, a read-only form field is submitted through a REST API with a changed value that bypasses UI rules. It does not verify the stated 2.2 requirement.
D:This test would assess another concern: During a change review of the scoped Project Intake app used for new project approvals, an after Business Rule calls current.update() every time a record changes and starts an execution loop. Previously created new project approvals records must remain valid after the change. It does not verify the stated 2.2 requirement.
Question 549
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test on insert and update with the correct trigger condition
- Run producer-to-target field reconciliation tests
- Use server authorization and avoid unnecessary synchronous calls
- Test missing and stale reference identifiers
Explanation
Correct Answer
C:Use server authorization and avoid unnecessary synchronous calls. It prevents the following recurring problem: Browser-side record access is not a substitute for controlled server-side logic.
Incorrect Answers
A:That safeguard addresses a different application case: 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 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 collects a contact date but the created record has a blank corresponding field. It does not control the cause here.
D:That safeguard addresses a different application case: In the scoped Service Requests app handling internal support requests, a Business Rule changes related task state without checking whether the related record actually exists. It does not control the cause here.
Question 550
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. Select THREE complementary measures or outcomes that address this case.
- Send entire confidential table to the client
- Grant broad read access so the browser query works
- Use server authorization and avoid unnecessary synchronous calls
- The form receives only the quota decision without leaking restricted rows
- Store admin credentials inside the Client Script
- Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax
Explanation
Correct Answers
C:Use server authorization and avoid unnecessary synchronous calls. It guards against the recurring issue: Browser-side record access is not a substitute for controlled server-side logic.
D:Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax. This is the direct observed result required before acceptance.
F:Expose narrowly scoped server logic through an authorized Script Include and asynchronous GlideAjax. The diagnosed cause is: Browser-side record access is not a substitute for controlled server-side logic.
Incorrect Answers
A:“Send entire confidential table to the client” would leave this failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
B:“Grant broad read access so the browser query works” would leave this failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
E:“Store admin credentials inside the Client Script” would leave this failure unresolved: Browser-side record access is not a substitute for controlled server-side logic.
ServiceNow Certified Application Developer (CAD) Practice Tests