100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 120
During a change review of the scoped Contract Renewals app used for renewal cases, a new application version introduces a regression and the team has no record of which artifact was installed. Previously created renewal cases records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Use the latest untested developer branch in production without checking existing renewal cases data
- Record repository version, installation receipt and tested rollback path and regression-test the existing renewal cases records
- Replace the version number with the date in a form title without checking existing renewal cases data
- Delete prior release records without checking existing renewal cases data
- A test instance can identify and recover from the failed candidate release for both old and new renewal cases records
- Retain signed deployment decisions and compatibility checks and keep a rollback plan for the Contract Renewals release
Explanation
Correct Answers
B:Record repository version, installation receipt and tested rollback path and regression-test the existing renewal cases records. The diagnosed cause is: Versioned application releases require manifest and rollback traceability; existing renewal cases also require backward-compatible behavior.
E:Record repository version, installation receipt and tested rollback path and regression-test the existing renewal cases records. This is the direct observed result required before acceptance.
F:Retain signed deployment decisions and compatibility checks and keep a rollback plan for the Contract Renewals release. It guards against the recurring issue: Versioned application releases require manifest and rollback traceability; existing renewal cases also require backward-compatible behavior.
Incorrect Answers
A:“Use the latest untested developer branch in production without checking existing renewal cases data” would leave this failure unresolved: Versioned application releases require manifest and rollback traceability; existing renewal cases also require backward-compatible behavior.
C:“Replace the version number with the date in a form title without checking existing renewal cases data” would leave this failure unresolved: Versioned application releases require manifest and rollback traceability; existing renewal cases also require backward-compatible behavior.
D:“Delete prior release records without checking existing renewal cases data” would leave this failure unresolved: Versioned application releases require manifest and rollback traceability; existing renewal cases also require backward-compatible behavior.
Question 121
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. What is the most appropriate supported design or corrective action?
- Grant admin to all requestors
- Use a public form for confidential requests
- Define submitter and approver roles and authorize each action through platform controls
- Hide the Approve button without a server-side check
Explanation
Correct Answer
C:Define submitter and approver roles and authorize each action through platform controls. The reason is that a good platform fit still requires role-specific access and least privilege.
Incorrect Answers
A:“Grant admin to all requestors” would leave the failure unresolved: A good platform fit still requires role-specific access and least privilege.
B:“Use a public form for confidential requests” would leave the failure unresolved: A good platform fit still requires role-specific access and least privilege.
D:“Hide the Approve button without a server-side check” would leave the failure unresolved: A good platform fit still requires role-specific access and least privilege.
Question 122
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- A good platform fit still requires role-specific access and least privilege
- Broad application resource exposure expands the callable surface; existing partner record synchronization also require backward-compatible behavior
- Navigation hiding is not a substitute for record- and operation-level authorization
- A textual field does not provide reliable numeric validation or aggregation; existing entitlement reviews also require backward-compatible behavior
Explanation
Correct Answer
A:Define submitter and approver roles and authorize each action through platform controls. The underlying issue is that a good platform fit still requires role-specific access and least privilege.
Incorrect Answers
B:This explanation belongs to another app case: 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 explain the failure here.
C:This explanation belongs to another app case: 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 explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped License Renewals app used for entitlement reviews, a table contains numeric equipment cost but the designer selects a plain string field for arithmetic totals. Previously created entitlement reviews records must remain valid after the change. It does not explain the failure here.
Question 123
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. After the proposed fix, which observation best proves the requirement was met?
- Role-based tests show submitters cannot approve their own protected records
- Two similarly named suppliers remain distinct in related records
- A changed display name resolves consistently without rewriting each request
- The app can be relabeled without breaking scoped script references
Explanation
Correct Answer
A:Role-based tests show submitters cannot approve their own protected records. This verifies the effect of define submitter and approver roles and authorize each action through platform controls.
Incorrect Answers
B:This test would assess another concern: In the scoped Vendor Onboarding app handling supplier qualification, a data model references a supplier using the supplier's nonunique trade name, creating collisions between regions. It does not verify the stated 1.1 requirement.
C:This test would assess another concern: 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 verify the stated 1.1 requirement.
D:This test would assess another concern: In the scoped Office Relocation app handling move requests, a developer renames a scoped application's display label and assumes its internal scope automatically changes. It does not verify the stated 1.1 requirement.
Question 124
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Define valid states and transition tests as part of the schema and keep a rollback plan for the Fleet Maintenance release
- Define valid states and transition tests as part of the schema
- Review cross-scope access log entries and regression-test blocked callers and keep a rollback plan for the Integration Reviews release
- Review personas, data ownership and privilege boundaries at design time
Explanation
Correct Answer
D:Review personas, data ownership and privilege boundaries at design time. It prevents the following recurring problem: A good platform fit still requires role-specific access and least privilege.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Fleet Maintenance app used for vehicle-service approvals, a request table uses two independent yes/no flags for a single mutually exclusive approval status. Previously created vehicle-service approvals 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 Inventory Transfers app handling movement requests, a request table uses two independent yes/no flags for a single mutually exclusive approval status. It does not control the cause here.
C:That safeguard addresses a different application case: 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 control the cause here.
Question 125
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. Select TWO complementary measures or outcomes that address this case.
- Role-based tests show submitters cannot approve their own protected records
- Define submitter and approver roles and authorize each action through platform controls
- Hide the Approve button without a server-side check
- Use a public form for confidential requests
- Grant admin to all requestors
Explanation
Correct Answers
A:Define submitter and approver roles and authorize each action through platform controls. This is the direct observed result required before acceptance.
B:Define submitter and approver roles and authorize each action through platform controls. The diagnosed cause is: A good platform fit still requires role-specific access and least privilege.
Incorrect Answers
C:“Hide the Approve button without a server-side check” would leave this failure unresolved: A good platform fit still requires role-specific access and least privilege.
D:“Use a public form for confidential requests” would leave this failure unresolved: A good platform fit still requires role-specific access and least privilege.
E:“Grant admin to all requestors” would leave this failure unresolved: A good platform fit still requires role-specific access and least privilege.
Question 126
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. What is the most appropriate supported design or corrective action?
- Keep a free-text string and guess dates in reports
- Hide the field when parsing fails
- Use a date-appropriate field and test valid input formats
- Make the date field a checkbox
Explanation
Correct Answer
C:Use a date-appropriate field and test valid input formats. The reason is that field type and input controls affect data validation and consistent storage.
Incorrect Answers
A:“Keep a free-text string and guess dates in reports” would leave the failure unresolved: Field type and input controls affect data validation and consistent storage.
B:“Hide the field when parsing fails” would leave the failure unresolved: Field type and input controls affect data validation and consistent storage.
D:“Make the date field a checkbox” would leave the failure unresolved: Field type and input controls affect data validation and consistent storage.
Question 127
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Field type and input controls affect data validation and consistent storage
- An unbounded GlideRecord query wastes resources and may process unrelated rows; existing inspection cases also require backward-compatible behavior
- Updating the same record in an after rule can recursively trigger Business Rules; existing new project approvals also require backward-compatible behavior
- Browser-side record access is not a substitute for controlled server-side logic; existing site-inspection records also require backward-compatible behavior
Explanation
Correct Answer
A:Use a date-appropriate field and test valid input formats. The underlying issue is that field type and input controls affect data validation and consistent storage.
Incorrect Answers
B: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.
C:This explanation belongs to another app case: 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 explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Field Safety app used for site-inspection records, a developer tries to call GlideRecord directly from a browser script to check a confidential quota. Previously created site-inspection records records must remain valid after the change. It does not explain the failure here.
Question 128
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. After the proposed fix, which observation best proves the requirement was met?
- Submitting the producer creates one correctly populated target record
- International users store consistent date values and reporting remains correct
- Rapid alternating selections leave the dependent value consistent with the final input for both old and new borrowed assets records
- The form consistently applies the same visible and mandatory rules across conditions for both old and new relocation checklists records
Explanation
Correct Answer
B:International users store consistent date values and reporting remains correct. This verifies the effect of use a date-appropriate field and test valid input formats.
Incorrect Answers
A:This test would assess another concern: In the scoped Service Request Intake app handling portal submissions, a catalog user needs to submit an application record without editing a table form directly. It does not verify the stated 2.1 requirement.
C:This test would assess another concern: During a change review of the scoped Equipment Loans app used for borrowed assets, a form automatically recalculates the wrong field when two dependent choices change rapidly. Previously created borrowed assets records must remain valid after the change. It does not verify the stated 2.1 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.1 requirement.
Question 129
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Use server authorization and avoid unnecessary synchronous calls
- Test on insert and update with the correct trigger condition
- Include non-admin API tests in security acceptance criteria and keep a rollback plan for the Lab Reservations release
- Document input locale and validate boundary dates
Explanation
Correct Answer
D:Document input locale and validate boundary dates. It prevents the following recurring problem: Field type and input controls affect data validation and consistent storage.
Incorrect Answers
A:That safeguard addresses a different application case: 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 control the cause here.
B: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.
C:That safeguard addresses a different application case: During a change review of the scoped Lab Reservations app used for instrument bookings, a Client Script checks the user's role to hide a sensitive form section. Previously created instrument bookings records must remain valid after the change. It does not control the cause here.
Question 130
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. Select THREE complementary measures or outcomes that address this case.
- Document input locale and validate boundary dates
- International users store consistent date values and reporting remains correct
- Use a date-appropriate field and test valid input formats
- Keep a free-text string and guess dates in reports
- Make the date field a checkbox
- Hide the field when parsing fails
Explanation
Correct Answers
A:Document input locale and validate boundary dates. It guards against the recurring issue: Field type and input controls affect data validation and consistent storage.
B:Use a date-appropriate field and test valid input formats. This is the direct observed result required before acceptance.
C:Use a date-appropriate field and test valid input formats. The diagnosed cause is: Field type and input controls affect data validation and consistent storage.
Incorrect Answers
D:“Keep a free-text string and guess dates in reports” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
E:“Make the date field a checkbox” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
F:“Hide the field when parsing fails” would leave this failure unresolved: Field type and input controls affect data validation and consistent storage.
ServiceNow Certified Application Developer (CAD) Practice Tests