ServiceNow CAD Practice Test

ServiceNow Certified Application Developer (CAD) is a developer-focused route for candidates who design, build, secure, and deploy custom applications on the ServiceNow platform.

This page includes 12 original sample questions for initial review. Full IT Mastery practice for ServiceNow CAD is not live yet; use the preview to test fit and use the Notify me form if this is the exam you want prioritized.

What this route should test

• choosing appropriate application, table, field, and data-model choices
• applying business logic, UI behavior, access control, and lifecycle concepts
• recognizing when scripting, declarative configuration, or platform features are the right fit
• troubleshooting why an application does not behave as intended

Common candidate trap

CAD practice should not reduce application development to syntax recall. Good questions test whether the candidate can choose a maintainable table design, enforce access correctly, place logic in the right layer, and avoid overusing scripts when configuration is enough.

Sample Exam Questions

These questions are original IT Mastery preview items for ServiceNow application-development judgment. They are not official ServiceNow exam questions.

Question 1

Topic: application design

A team wants a custom app for equipment requests. Requests need approval, task creation, and reporting by department. What should the developer clarify first?

• A. The business process, data model, roles, approval rules, and reporting needs
• B. The colour of the app icon only
• C. Whether every user should be admin
• D. Whether reports can be deleted

Best answer: A

Explanation: A custom app should start with process, data, access, and reporting requirements. Cosmetic choices do not define whether the app will support the workflow.

Question 2

Topic: table design

A custom table needs to store records that behave like task records with assignment and state tracking. What should the developer consider?

• A. A random text field for every task attribute
• B. Whether extending a task-related table or using a suitable table structure supports the required behavior
• C. A public dashboard folder only
• D. Removing all states

Best answer: B

Explanation: Table design affects inherited fields, process behavior, reporting, and maintainability. The developer should evaluate whether extension or a standalone table fits the workflow.

Question 3

Topic: business logic

A validation must run whenever a record is saved, regardless of which form or integration updates it. Where should the rule generally live?

• A. In a user’s browser bookmark
• B. In a report title
• C. Server-side business logic that runs on record operations
• D. In an email signature

Best answer: C

Explanation: Logic that must apply across forms, imports, and integrations should not depend only on client-side behavior. Server-side logic is more reliable for record-save enforcement.

Question 4

Topic: client behavior

A form should show a warning immediately when a user changes a field before saving. What layer is most relevant?

• A. A scheduled report only
• B. A data retention policy only
• C. A new module name
• D. Client-side form behavior such as a client script or UI policy

Best answer: D

Explanation: Immediate form interaction before save is client-side behavior. UI policies or client scripts are common choices depending on the requirement.

Question 5

Topic: access control

A custom app stores confidential review notes. Only review managers should read the notes field. What should the developer configure?

• A. Field/table access controls and roles that match the manager requirement
• B. A public list view
• C. A dashboard colour
• D. An unrestricted import set

Best answer: A

Explanation: Sensitive fields require explicit access design. Roles and ACLs should enforce who can read or write the field, independent of visual layout.

Question 6

Topic: script placement

A developer wants to reuse the same server-side calculation from several places in an application. What design is usually stronger?

• A. Copy the same script into every rule
• B. Put reusable logic in an appropriate shared server-side component and call it where needed
• C. Ask users to calculate manually
• D. Store the formula in the app description

Best answer: B

Explanation: Reusable server-side logic improves maintainability and reduces inconsistent behavior. Copying logic across many places creates drift.

Question 7

Topic: flow versus script

A simple approval workflow can be built declaratively without custom script. What is the best development principle?

• A. Use script even when it adds unnecessary complexity
• B. Avoid documenting the solution
• C. Prefer a maintainable declarative solution when it satisfies the requirement
• D. Disable approvals

Best answer: C

Explanation: ServiceNow development often rewards choosing the simplest maintainable platform feature. Custom script should solve a real gap, not replace clear configuration by default.

Question 8

Topic: update sets and deployment

A developer is ready to move app configuration to test. What should happen before deployment?

• A. Delete the source application
• B. Ignore all update-set warnings
• C. Give all testers admin rights permanently
• D. Review captured changes, preview the update set, resolve issues, and test with representative users

Best answer: D

Explanation: Deployment discipline matters for CAD. The developer should verify what is captured, preview conflicts, resolve errors, and test the app in realistic contexts.

Question 9

Topic: data model

An app tracks projects and project risks. Each risk belongs to one project, and each project can have many risks. What relationship is most likely needed?

• A. A reference from Risk to Project
• B. A single text field listing all risks
• C. A dashboard widget only
• D. A deleted relationship

Best answer: A

Explanation: A reference relationship supports many risk records pointing to one project. Text lists are hard to secure, report, and automate reliably.

Question 10

Topic: troubleshooting

A business rule does not run when expected. What should the developer check first?

• A. Whether the app logo is square
• B. Rule conditions, timing, table, active status, order, and execution context
• C. Whether all reports are public
• D. Whether users like the field label

Best answer: B

Explanation: Business-rule behavior depends on where and when it runs, whether conditions match, and whether it is active on the correct table and operation.

Question 11

Topic: application scope

A script in a scoped application needs to interact with a platform resource outside the scope. What should the developer consider?

• A. Renaming every table
• B. Exporting all records to CSV
• C. Scope boundaries, cross-scope access, and whether the interaction is permitted and maintainable
• D. Removing the application scope

Best answer: C

Explanation: Application scope protects boundaries. Developers should understand cross-scope permissions and avoid unsafe shortcuts that make the app fragile.

Question 12

Topic: UI actions

A button should appear only when a record is in Draft and the user has an approver role. What should control the button?

• A. The user’s browser size
• B. The instance time zone only
• C. A random hidden field
• D. UI action conditions or equivalent visibility logic based on state and role

Best answer: D

Explanation: Button visibility should be controlled by explicit conditions tied to record state and user permissions. This keeps the UI aligned with the process.

CAD quick checklist

Related ServiceNow pages

• Certified System Administrator
• CIS-ITSM
• ServiceNow certification updates