100% Latest & Updated ServiceNow CAD Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
During a change review of the scoped Security Exceptions app used for protected case records, a delegated developer can edit some artifacts but cannot alter all security ACLs. Previously created protected case records records must remain valid after the change. Select THREE complementary measures or outcomes that address this case.
- Grant permanent security_admin to every delegate without checking existing protected case records data
- Test delegated privileges separately from security elevation and keep a rollback plan for the Security Exceptions release
- Allowed development continues while protected ACL operations remain controlled for both old and new protected case records records
- Disable ACL checks for all developers without checking existing protected case records data
- Use a Client Script to replace ACL rules without checking existing protected case records data
- Route ACL security changes through the authorized security_admin review process and regression-test the existing protected case records records
Explanation
Correct Answers
B:Test delegated privileges separately from security elevation and keep a rollback plan for the Security Exceptions release. It guards against the recurring issue: Delegated app development does not automatically bypass separately elevated security privileges; existing protected case records also require backward-compatible behavior.
C:Route ACL security changes through the authorized security_admin review process and regression-test the existing protected case records records. This is the direct observed result required before acceptance.
F:Route ACL security changes through the authorized security_admin review process and regression-test the existing protected case records records. The diagnosed cause is: Delegated app development does not automatically bypass separately elevated security privileges; existing protected case records also require backward-compatible behavior.
Incorrect Answers
A:“Grant permanent security_admin to every delegate without checking existing protected case records data” would leave this failure unresolved: Delegated app development does not automatically bypass separately elevated security privileges; existing protected case records also require backward-compatible behavior.
D:“Disable ACL checks for all developers without checking existing protected case records data” would leave this failure unresolved: Delegated app development does not automatically bypass separately elevated security privileges; existing protected case records also require backward-compatible behavior.
E:“Use a Client Script to replace ACL rules without checking existing protected case records data” would leave this failure unresolved: Delegated app development does not automatically bypass separately elevated security privileges; existing protected case records also require backward-compatible behavior.
Question 361
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. What is the most appropriate supported design or corrective action?
- Match users by their screen name alone
- Copy the user profile into every text field
- Make the name field longer
- Use an appropriate reference field to the authorized user record
Explanation
Correct Answer
D:Use an appropriate reference field to the authorized user record. The reason is that a string copy loses referential integrity and reliable linkage to the existing person record.
Incorrect Answers
A:“Match users by their screen name alone” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
B:“Copy the user profile into every text field” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
C:“Make the name field longer” would leave the failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
Question 362
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. Which explanation best identifies the underlying ServiceNow application-development problem?
- A string copy loses referential integrity and reliable linkage to the existing person record
- Cross-scope runtime access requires allowed target settings and authorized privileges; existing internal support requests also require backward-compatible behavior
- Display name and immutable technical identifiers serve different purposes; existing planned outages also require backward-compatible behavior
- The need is a multi-user case workflow rather than a one-off document generator
Explanation
Correct Answer
A:Use an appropriate reference field to the authorized user record. The underlying issue is that a string copy loses referential integrity and reliable linkage to the existing person record.
Incorrect Answers
B:This explanation belongs to another app case: During a change review of the scoped Service Requests app used for internal support requests, a scoped script calls a Script Include in another application and is denied at runtime. Previously created internal support requests 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 Maintenance Windows app used for planned outages, a developer renames a scoped application's display label and assumes its internal scope automatically changes. Previously created planned outages records must remain valid after the change. It does not explain the failure here.
D:This explanation belongs to another app case: In the scoped Site Visits app handling visitor authorizations, an app proposal requires staff to see work assigned to their team across many handoffs and a shared status timeline. It does not explain the failure here.
Question 363
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. After the proposed fix, which observation best proves the requirement was met?
- Two teams can hand off records while preserving status and ownership history for both old and new inspection cases records
- A changed display name resolves consistently without rewriting each request
- Authorized staff can navigate to the expected list from the application menu
- An authorized caller succeeds while an unrelated scope remains blocked
Explanation
Correct Answer
B:A changed display name resolves consistently without rewriting each request. This verifies the effect of use an appropriate reference field to the authorized user record.
Incorrect Answers
A:This test would assess another concern: During a change review of the scoped Quality Inspections app used for inspection cases, an app proposal requires staff to see work assigned to their team across many handoffs and a shared status timeline. Previously created inspection cases records must remain valid after the change. It does not verify the stated 1.2 requirement.
C:This test would assess another concern: In the scoped Incident Follow-ups app handling follow-up tasks, a scoped application exists but staff cannot find its list in the All navigation menu. It does not verify the stated 1.2 requirement.
D: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.2 requirement.
Question 364
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. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Map the actual business handoff and exception paths before implementation and keep a rollback plan for the Quality Inspections release
- Document process owners and the workflow boundary before building and keep a rollback plan for the Project Intake release
- Test reference targets and ACLs against non-admin personas
- Freeze scope/API naming early and review any migration needs separately and keep a rollback plan for the Maintenance Windows release
Explanation
Correct Answer
C:Test reference targets and ACLs against non-admin personas. It prevents the following recurring problem: A string copy loses referential integrity and reliable linkage to the existing person record.
Incorrect Answers
A:That safeguard addresses a different application case: During a change review of the scoped Quality Inspections app used for inspection cases, an app proposal requires staff to see work assigned to their team across many handoffs and a shared status timeline. Previously created inspection cases 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.
D:That safeguard addresses a different application case: During a change review of the scoped Maintenance Windows app used for planned outages, a developer renames a scoped application's display label and assumes its internal scope automatically changes. Previously created planned outages records must remain valid after the change. It does not control the cause here.
Question 365
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. Select TWO complementary measures or outcomes that address this case.
- A changed display name resolves consistently without rewriting each request
- Copy the user profile into every text field
- Use an appropriate reference field to the authorized user record
- Make the name field longer
- Match users by their screen name alone
Explanation
Correct Answers
A:Use an appropriate reference field to the authorized user record. This is the direct observed result required before acceptance.
C:Use an appropriate reference field to the authorized user record. The diagnosed cause is: A string copy loses referential integrity and reliable linkage to the existing person record.
Incorrect Answers
B:“Copy the user profile into every text field” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
D:“Make the name field longer” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
E:“Match users by their screen name alone” would leave this failure unresolved: A string copy loses referential integrity and reliable linkage to the existing person record.
Question 366
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. What is the most appropriate supported design or corrective action?
- Configure a UI Policy with a condition and mandatory field action
- Require the field for every request type
- Use an ACL as a form-required indicator
- Add an after Business Rule solely to change browser appearance
Explanation
Correct Answer
A:Configure a UI Policy with a condition and mandatory field action. The reason is that a declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Incorrect Answers
B:“Require the field for every request type” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
C:“Use an ACL as a form-required indicator” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
D:“Add an after Business Rule solely to change browser appearance” would leave the failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Question 367
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Which explanation best identifies the underlying ServiceNow application-development problem?
- Multiple UI-specific defaults can disagree with server-side record creation paths; existing risk acknowledgments also require backward-compatible behavior
- The previous object is not a meaningful prior stored record during an insert; existing move requests also require backward-compatible behavior
- Field type and input controls affect data validation and consistent storage; existing course requests also require backward-compatible behavior
- A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script
Explanation
Correct Answer
D:Configure a UI Policy with a condition and mandatory field action. The underlying issue is that a declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Incorrect Answers
A:This explanation belongs to another app case: During a change review of the scoped Security Exceptions app used for risk acknowledgments, a developer needs a default value for a classification field but hard-codes it in several form scripts. Previously created risk acknowledgments 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 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 explain the failure here.
C:This explanation belongs to another app case: During a change review of the scoped Training Enrollment app used for course requests, a form uses a string field to collect a date and users enter ambiguous regional text. Previously created course requests records must remain valid after the change. It does not explain the failure here.
Question 368
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. 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
- Changing Emergency on and off updates the required field consistently
- Authorized staff see only the related records for the current parent
- Both UI and API invalid writes are rejected consistently
Explanation
Correct Answer
B:Changing Emergency on and off updates the required field consistently. This verifies the effect of configure a UI Policy with a condition and mandatory field action.
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 Office Relocation app handling move requests, a staff form omits a related list needed to inspect the child's requests. It does not verify the stated 2.2 requirement.
D: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.
Question 369
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Which ongoing guardrail specifically lowers the risk of this defect recurring?
- Test on insert and update with the correct trigger condition
- Review query cardinality and server-side ACL expectations and keep a rollback plan for the Quality Inspections release
- Detect recursion and log only bounded rule invocations and keep a rollback plan for the Project Intake release
- Test policy reverse behavior and conflict with existing client scripts
Explanation
Correct Answer
D:Test policy reverse behavior and conflict with existing client scripts. It prevents the following recurring problem: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
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: 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 control the cause here.
C:That safeguard addresses a different application 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 control the cause here.
Question 370
In the scoped Facilities Repairs app handling repair requests, a field should be mandatory only when the request type equals Emergency, with no custom computation. Select THREE complementary measures or outcomes that address this case.
- Test policy reverse behavior and conflict with existing client scripts
- Add an after Business Rule solely to change browser appearance
- Changing Emergency on and off updates the required field consistently
- Require the field for every request type
- Configure a UI Policy with a condition and mandatory field action
- Use an ACL as a form-required indicator
Explanation
Correct Answers
A:Test policy reverse behavior and conflict with existing client scripts. It guards against the recurring issue: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
C:Configure a UI Policy with a condition and mandatory field action. This is the direct observed result required before acceptance.
E:Configure a UI Policy with a condition and mandatory field action. The diagnosed cause is: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
Incorrect Answers
B:“Add an after Business Rule solely to change browser appearance” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
D:“Require the field for every request type” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
F:“Use an ACL as a form-required indicator” would leave this failure unresolved: A declarative UI Policy can control conditional visible, mandatory and read-only behavior without script.
ServiceNow Certified Application Developer (CAD) Practice Tests