100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 1
In the scoped Work Permit Intake app handling permit requests, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. What is the most appropriate supported design or corrective action?
- Model the approvals as a scoped app with records, states, roles and audit evidence
- Store every approval in a shared spreadsheet
- Remove the audit fields to simplify the form
- Hard-code approver email addresses in a browser script
Explanation
Correct Answer
A:Model the approvals as a scoped app with records, states, roles and audit evidence. The reason is that a structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
Incorrect Answers
B:“Store every approval in a shared spreadsheet” would leave the failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
C:“Remove the audit fields to simplify the form” would leave the failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
D:“Hard-code approver email addresses in a browser script” would leave the failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
Question 2
In the scoped Work Permit Intake app handling permit requests, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. Which explanation best identifies the underlying ServiceNow application-development problem?
- A single reference field cannot represent a many-to-many association
- Broad application resource exposure expands the callable surface
- A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file
- Uncontrolled text permits inconsistent categories and unreliable aggregation
Explanation
Correct Answer
C:Model the approvals as a scoped app with records, states, roles and audit evidence. The underlying issue is that a structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Security Exceptions app handling risk acknowledgments, a review record must link to many evidence documents and each document can support many reviews. 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 cross-scope resource should be called only by a known integration app, but all scopes are permitted. It does not explain the failure here.
D:This explanation belongs to another app case: In the scoped Lab Reservations app handling instrument bookings, reports group the same category as different values because free-text entries vary in spelling. It does not explain the failure here.
Question 3
In the scoped Work Permit Intake app handling permit requests, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. After the proposed fix, which observation best proves the requirement was met?
- An authorized caller succeeds while an unrelated scope remains blocked
- A clean install resolves expected scoped tables, roles and script references
- Reports show one governed category per intended class
- Requests follow authorized approvals and retain a traceable decision history
Explanation
Correct Answer
D:Requests follow authorized approvals and retain a traceable decision history. This verifies the effect of model the approvals as a scoped app with records, states, roles and audit evidence.
Incorrect Answers
A:This test would assess another concern: In the scoped Training Waivers app handling policy exemptions, a scoped script calls a Script Include in another application and is denied at runtime. It does not verify the stated 1.1 requirement.
B:This test would assess another concern: In the scoped Visitor Badging app handling temporary credentials, a team starts a new scoped app without checking its name, scope and target instance and later must remap references. It does not verify the stated 1.1 requirement.
C:This test would assess another concern: In the scoped Lab Reservations app handling instrument bookings, reports group the same category as different values because free-text entries vary in spelling. It does not verify the stated 1.1 requirement.
Question 4
In the scoped Work Permit Intake app handling permit requests, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Review application-file namespace and dependencies before export and keep a rollback plan for the Asset Disposal release
- Test inherited rules and ACL behavior in a nonproduction instance
- Use field type standards and sample-data tests during data-model review
- Document process owners and the workflow boundary before building
Explanation
Correct Answer
D:Document process owners and the workflow boundary before building. It prevents the following recurring problem: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
Incorrect Answers
A:That safeguard addresses a different application case: 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 control the cause here.
B:That safeguard addresses a different application case: In the scoped Facilities Access app handling building-entry requests, a custom case shares assignment and state behavior with task records but also has its own approval reason. It does not control the cause here.
C:That safeguard addresses a different application case: 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. It does not control the cause here.
Question 5
In the scoped Work Permit Intake app handling permit requests, a team wants a custom approval app for requests, assignments, status history and audit trails, but proposes a stand-alone spreadsheet macro. Select TWO complementary measures or outcomes that address this case.
- Store every approval in a shared spreadsheet
- Remove the audit fields to simplify the form
- Model the approvals as a scoped app with records, states, roles and audit evidence
- Hard-code approver email addresses in a browser script
- Requests follow authorized approvals and retain a traceable decision history
Explanation
Correct Answers
C:Model the approvals as a scoped app with records, states, roles and audit evidence. The diagnosed cause is: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
E:Model the approvals as a scoped app with records, states, roles and audit evidence. This is the direct observed result required before acceptance.
Incorrect Answers
A:“Store every approval in a shared spreadsheet” would leave this failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
B:“Remove the audit fields to simplify the form” would leave this failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
D:“Hard-code approver email addresses in a browser script” would leave this failure unresolved: A structured workflow with records, roles and approval history fits the Now Platform better than an isolated file.
Question 6
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. What is the most appropriate supported design or corrective action?
- Delete the table field to simplify one screen
- Adjust the appropriate form view and sections for each persona
- Move the value to an unvalidated note
- Give every role the same administrator view
Explanation
Correct Answer
B:Adjust the appropriate form view and sections for each persona. The reason is that a form layout is a view of a record and can be tailored without changing underlying table storage.
Incorrect Answers
A:“Delete the table field to simplify one screen” would leave the failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
C:“Move the value to an unvalidated note” would leave the failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
D:“Give every role the same administrator view” would leave the failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
Question 7
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- Unrestricted Business Rule conditions cause unnecessary actions and duplicates
- An onChange handler can run during loading and should avoid unnecessary server calls
- A form layout is a view of a record and can be tailored without changing underlying table storage
- An onSubmit Client Script can validate the current form before sending it; existing movement requests also require backward-compatible behavior
Explanation
Correct Answer
C:Adjust the appropriate form view and sections for each persona. The underlying issue is that a form layout is a view of a record and can be tailored without changing underlying table storage.
Incorrect Answers
A:This explanation belongs to another app case: In the scoped Purchase Approvals app handling purchasing records, a Business Rule executes for every update even when the required status transition did not occur. It does not explain the failure here.
B:This explanation belongs to another app 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 explain the failure here.
D:This explanation belongs to another app case: During a change review of the scoped Inventory Transfers app used for movement requests, a submit form must reject invalid overlapping date ranges before save. Previously created movement requests records must remain valid after the change. It does not explain the failure here.
Question 8
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. After the proposed fix, which observation best proves the requirement was met?
- Invalid submissions are stopped with a clear message, while valid records save
- Create and update tests take intended branches without null references for both old and new move requests records
- Reviewers see the intended fields while the table data remains intact
- Rapid alternating selections leave the dependent value consistent with the final input
Explanation
Correct Answer
C:Reviewers see the intended fields while the table data remains intact. This verifies the effect of adjust the appropriate form view and sections for each persona.
Incorrect Answers
A:This test would assess another concern: In the scoped Visitor Badging app handling temporary credentials, a submit form must reject invalid overlapping date ranges before save. It does not verify the stated 2.1 requirement.
B:This test would assess another concern: 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 verify the stated 2.1 requirement.
D:This test would assess another concern: In the scoped Supplier Reviews app handling vendor assessments, a form automatically recalculates the wrong field when two dependent choices change rapidly. It does not verify the stated 2.1 requirement.
Question 9
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Review query cardinality and server-side ACL expectations
- Test nonmatching updates and repeated saves for idempotency and keep a rollback plan for the Training Waivers release
- Review form-view changes with each intended user role
- Retain corresponding server-side validation for API and non-browser writes
Explanation
Correct Answer
C:Review form-view changes with each intended user role. It prevents the following recurring problem: A form layout is a view of a record and can be tailored without changing underlying table storage.
Incorrect Answers
A:That safeguard addresses a different application case: In the scoped Site Visits app handling visitor authorizations, a server script queries all historical records and iterates them to find one known sys_id. It does not control the cause here.
B:That safeguard addresses a different application 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 control the cause here.
D:That safeguard addresses a different application case: In the scoped Visitor Badging app handling temporary credentials, a submit form must reject invalid overlapping date ranges before save. It does not control the cause here.
Question 10
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. Select THREE complementary measures or outcomes that address this case.
- Reviewers see the intended fields while the table data remains intact
- Delete the table field to simplify one screen
- Adjust the appropriate form view and sections for each persona
- Review form-view changes with each intended user role
- Move the value to an unvalidated note
- Give every role the same administrator view
Explanation
Correct Answers
A:Adjust the appropriate form view and sections for each persona. This is the direct observed result required before acceptance.
C:Adjust the appropriate form view and sections for each persona. The diagnosed cause is: A form layout is a view of a record and can be tailored without changing underlying table storage.
D:Review form-view changes with each intended user role. It guards against the recurring issue: A form layout is a view of a record and can be tailored without changing underlying table storage.
Incorrect Answers
B:“Delete the table field to simplify one screen” would leave this failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
E:“Move the value to an unvalidated note” would leave this failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
F:“Give every role the same administrator view” would leave this failure unresolved: A form layout is a view of a record and can be tailored without changing underlying table storage.
ServiceNow Certified Application Developer (CAD) Practice Tests