Free ServiceNow CAD Actual Exam Questions

D, B. jslog() is definitely meant for client-side, and g_form.addInfoMessage() lets you show messages directly on the form, which can help track what's happening during script execution.

It’s D for sure since jslog() is built for client-side debugging. For the second, I’d go with B. g_form.addInfoMessage() isn’t just for user info; it can be handy to quickly check values or states during debugging on client scripts. A and C are more server-side or error-reporting focused, so they don’t fit as well for debugging client-side issues.

B imo, related links are useful for extra info but not great for core instructions since users might miss them or ignore the links. Instructions should be right there on the form.

Maybe D works too since a read-only field can show instructions right in the form without extra clicks. It’s more direct than relying on users to open menus or follow links.

Maybe C, E, and D? I know scripting is a big part of customizing record producers, so D could make sense if they mean scripting to control field behaviors or validation. A and B seem less related since not all record producers add graphics, and B is only true for ones tied to requested items. E fits because it’s about the user experience with prompts instead of labels. So I’d pick the scripting options plus the prompting one.

Option C, E, and B fit best since scripting prompts and often targets sc_req_item.

It’s D, queries often happen outside strict app controls and can’t be fully blocked.

Maybe D, queries often bypass strict app controls unlike create/update/delete.

Not C; “Standard” is vague, and forms and lists usually need specialized formats.

I’m thinking D because “Classic” might mean the most tested, reliable format here. D

E imo, because Caller Restriction deals directly with access levels, F fits as it relates to permissions, and B seems correct since “Accessible from” indicates where the access applies. The others don’t sound like fields.

It’s B, E, and F because A sounds more like a feature, not an access field.

This isn’t about strings or dates since those just store data without linking. The key is that you want to query records from another table, which means you need a field that points directly to those records. That’s why the Reference field (B) fits best—it’s designed to create a relationship and pull data dynamically. Phone number fields (A) are just for storing numbers, not linking, so they don’t make sense here. So yeah, B is the right call for setting up queries across tables within a form.

Maybe B, since a reference field directly links tables, unlike strings or dates.

A, because it specifically measures open task duration before escalation.

Option A seems right because the Task Escalation Clock tracks how long a task has been open and triggers escalation if it’s overdue, which fits the need to monitor total open time.

D imo, since update sets track changes but aren’t the repo itself. The App Repository sounds more like a central place for storing apps, not just a Git file collection, so C still feels right from that angle.

I agree with C here. The App Repository is basically a database holding the different apps you can install or manage on the platform. It’s not just a simple table (A) or a name for update sets (B), and D seems unlikely because ServiceNow doesn’t use Git as its main storage for apps inside the platform. So, C fits best as it captures the idea of a centralized place where ServiceNow apps are stored.

D, because only Spokes are designed to package reusable flow actions within scoped apps.

It’s D for sure. Spokes are made to package flow actions for reuse, while the other options don’t really relate to scoped apps or flow actions in ServiceNow.

C/D? The "Include data" flag definitely impacts whether records get installed, but the "Create Application Files" feature is how you actually add those records to the app. Both seem necessary for full installation.

Makes sense that the auto number doesn’t really matter here because it’s more about record creation than installation. The key seems to be having “Include data” checked for the table, so I’d go with C. Also, D sounds plausible but I don’t think you manually add records that way for installation.

B imo, this option just controls whether the table can be accessed over web services at all. It doesn’t override user permissions, so even if it’s selected, users still need the right roles to read or modify data. A and D sound off because the setting isn’t about limiting deletes or only SOAP access. C is wrong since if the option isn’t selected, web service access is basically blocked regardless of permissions. So B fits best for how access and permissions work together here.

B This option basically just enables access through web services, but the user still needs the right permissions to actually see or modify records. Without those permissions, nothing changes. So it’s not like it opens the door for everyone, just allows web service calls if permissions are there. Makes sense that permissions remain the gatekeeper here.

A/D? Caller tracking records might make sense since they track who calls what, and access control level records define permissions, so either could be valid depending on context.

I feel like C is the best match since it literally says cross-scope access records. C

Option C since the syntax is clearly wrong, so the method might not actually exist.

This one’s definitely D. The hasRole method strictly checks for the given role, and it won’t return true just because the user has some other role like admin. The syntax looks a bit funky but that doesn’t change how hasRole behaves—it’s role-specific. A is out because admin isn’t included implicitly, and C is incorrect since hasRole is a valid method. B is the opposite of what hasRole does, so no chance there.

D imo, generating an event alongside setting field values is something Business Rules can handle without scripting, especially for triggering other processes. Querying the database or logging usually needs scripts, so A and C feel off. Adding messages (B) is common, but events are more aligned with automated workflows, making D a solid pick.

B/C? Setting field values is definitely standard for Business Rules, and adding messages feels like a simple built-in feature. Writing to the system log seems less straightforward without scripting, but it could be possible since logs are basic system feedback. Querying the database and generating events usually require more behind-the-scenes coding, so I’m ruling those out. Between B and C, I’d say adding messages (B) is more commonly mentioned, but the system log (C) might still be doable without scripting in some cases.