ServiceNow CAD Practice Test 80
Question 790
An app must evaluate pending reminders each night regardless of user logins. Which approach BEST meets the requirement while respecting the system constraints?
- Configure a Scheduled Script Execution with an appropriate supported schedule.
- Supply documented event parameters when queuing the event and consume them safely.
- Trigger the job solely from a user's browser refresh and call it a reliable nightly schedule.
- Move reusable logic into a scoped utility Script Include and call it from permitted server contexts.
Explanation
Correct Answer
A:Configure a Scheduled Script Execution with an appropriate supported schedule. Scheduled scripts run server logic according to schedule settings independent of interactive form updates. Verification should demonstrate that the job runs at the expected time and logs the processed record count.
Incorrect Answers
B:Supply documented event parameters when queuing the event and consume them safely. This primarily addresses Event parameters for notifications, not the specific Scheduled Script Execution timing decision. Here, scheduled scripts run server logic according to schedule settings independent of interactive form updates.
C:Trigger the job solely from a user's browser refresh and call it a reliable nightly schedule. This is an unsafe or ineffective shortcut for Scheduled Script Execution timing. Incorrect schedules can skip deadlines or run too frequently.
D:Move reusable logic into a scoped utility Script Include and call it from permitted server contexts. This primarily addresses Utility Script Include for scheduled jobs, not the specific Scheduled Script Execution timing decision. Here, scheduled scripts run server logic according to schedule settings independent of interactive form updates.
Question 791
An administrator wants to declutter a form while preserving reports. Select TWO statements that correctly combine the Remove fields from view without deleting data method with evidence or its governing principle.
- Configure a suitable reference qualifier for the target reference field.
- Remove the field from the relevant form view rather than deleting its dictionary definition.
- Historical values remain retrievable to authorized users outside the simplified view.
- Define a new correctly typed table field and expose it on the required form.
- Delete the table column every time a field must disappear visually.
Explanation
Correct Answers
B:Remove the field from the relevant form view rather than deleting its dictionary definition. This is the intended action for Remove fields from view without deleting data.
C:Historical values remain retrievable to authorized users outside the simplified view. This is directly observable validation of the Remove fields from view without deleting data result.
Incorrect Answers
A:Configure a suitable reference qualifier for the target reference field. This serves the different Reference qualifier for valid selections objective, not the selected Remove fields from view without deleting data plan. Removing a field from a form is different from removing the field from the table.
D:Define a new correctly typed table field and expose it on the required form. This serves the different Add fields from the table dictionary objective, not the selected Remove fields from view without deleting data plan. Removing a field from a form is different from removing the field from the table.
E:Delete the table column every time a field must disappear visually. This is not part of a safe or effective Remove fields from view without deleting data design. Deleting a dictionary field can affect retained data and dependent business logic.
Question 792
A manager needs an extra due date in saved case records rather than a visual note. After the recommended Add fields from the table dictionary change is implemented, which observation MOST directly verifies that it works?
- Historical values remain retrievable to authorized users outside the simplified view.
- Each intended role or context sees the proper fields without bypassing record security.
- Lookup choices match expected filter conditions for the test records.
- The field persists and is queryable across records and lists.
Explanation
Correct Answer
D:The field persists and is queryable across records and lists. This directly tests whether the Add fields from the table dictionary goal was met. Table columns hold persisted values while form configuration determines display.
Incorrect Answers
A:Historical values remain retrievable to authorized users outside the simplified view. This is evidence about Remove fields from view without deleting data, not direct proof of the required Add fields from the table dictionary behavior. The relevant check is that the field persists and is queryable across records and lists.
B:Each intended role or context sees the proper fields without bypassing record security. This is evidence about Multiple form views by persona, not direct proof of the required Add fields from the table dictionary behavior. The relevant check is that the field persists and is queryable across records and lists.
C:Lookup choices match expected filter conditions for the test records. This is evidence about Reference qualifier for valid selections, not direct proof of the required Add fields from the table dictionary behavior. The relevant check is that the field persists and is queryable across records and lists.
Question 793
A CSV import uses column names identical to those in the target table. Which approach BEST meets the requirement while respecting the system constraints?
- Use Auto Map Matching Fields and manually review unmatched or incorrect mappings.
- Assume Auto Map Matching Fields infers every foreign-key and unit conversion automatically.
- Mark a suitable unique field map as Coalesce and validate key uniqueness.
- Use a tested Transform Map field script or transform script for the necessary conversion.
Explanation
Correct Answer
A:Use Auto Map Matching Fields and manually review unmatched or incorrect mappings. Auto-map assists matching field names but cannot infer every semantic transformation. Verification should demonstrate that direct name matches map and remaining fields receive reviewed explicit maps.
Incorrect Answers
B:Assume Auto Map Matching Fields infers every foreign-key and unit conversion automatically. This is an unsafe or ineffective shortcut for Auto Map Matching Fields limits. Unexamined auto mapping can omit fields whose source names differ.
C:Mark a suitable unique field map as Coalesce and validate key uniqueness. This primarily addresses Coalesce for update versus insert, not the specific Auto Map Matching Fields limits decision. Here, auto-map assists matching field names but cannot infer every semantic transformation.
D:Use a tested Transform Map field script or transform script for the necessary conversion. This primarily addresses Transform scripts for calculated mappings, not the specific Auto Map Matching Fields limits decision. Here, auto-map assists matching field names but cannot infer every semantic transformation.
Question 794
An application manager needs to authorize limited Git operations for one delegated developer. Which practical correction or implementation decision is MOST directly appropriate?
- Replace source-control permission reviews by granting global admin to every contributor.
- Configure a delegated developer and verify the least-privilege file permissions.
- Require peer review and platform testing before promotion.
- Set scoped source control permissions and validate access boundaries.
Explanation
Correct Answer
D:Set scoped source control permissions and validate access boundaries. The intended behavior can be checked because the authorized developer sees source control commands only for the intended app.
Incorrect Answers
A:Replace source-control permission reviews by granting global admin to every contributor. This would not correct the Delegated source-control authorization workflow. File-edit permission alone need not imply permission to change repository links.
B:Configure a delegated developer and verify the least-privilege file permissions. This could help Delegated Development for privately scoped apps, but it does not resolve the Delegated source-control authorization case. Source control rights may be assigned separately from general delegated editing.
C:Require peer review and platform testing before promotion. This could help Code review and scoped contribution workflow, but it does not resolve the Delegated source-control authorization case. Source control rights may be assigned separately from general delegated editing.
Question 795
An application needs testable common server-side logic used by many scripts. Which practical correction or implementation decision is MOST directly appropriate?
- Insert the full shared function separately into every rule and maintain inconsistent copies.
- Test before-rule conditions and ensure no unnecessary recursive updates.
- Keep synchronous invariants separate from safe async follow-up.
- Refactor common validation into a named scoped utility with unit tests.
Explanation
Correct Answer
D:Refactor common validation into a named scoped utility with unit tests. The intended behavior can be checked because multiple callers get consistent results with one maintained implementation.
Incorrect Answers
A:Insert the full shared function separately into every rule and maintain inconsistent copies. This would not correct the Script Include utility reuse workflow. Duplicate code increases divergence and makes corrections error-prone.
B:Test before-rule conditions and ensure no unnecessary recursive updates. This could help Before Business Rule validation, but it does not resolve the Script Include utility reuse case. Script Includes support reusable server-side JavaScript rather than copying logic across rules.
C:Keep synchronous invariants separate from safe async follow-up. This could help Async Business Rule processing, but it does not resolve the Script Include utility reuse case. Script Includes support reusable server-side JavaScript rather than copying logic across rules.
Question 796
A flow triggers but never creates the expected related task. Which approach BEST meets the requirement while respecting the system constraints?
- Extract shared logic into a subflow with typed inputs and documented outputs.
- Inspect the flow execution details and failing step outcomes in the permitted environment.
- Delete flow execution records and report success without examining errors.
- Configure the correct record-based flow trigger and conditions for the target table.
Explanation
Correct Answer
B:Inspect the flow execution details and failing step outcomes in the permitted environment. Execution history and logs support diagnosis beyond assuming the flow ran. Verification should demonstrate that evidence identifies trigger record, step inputs, error and controlled correction.
Incorrect Answers
A:Extract shared logic into a subflow with typed inputs and documented outputs. This primarily addresses Reusable subflow design, not the specific Flow execution logs and troubleshooting decision. Here, execution history and logs support diagnosis beyond assuming the flow ran.
C:Delete flow execution records and report success without examining errors. This is an unsafe or ineffective shortcut for Flow execution logs and troubleshooting. Without step-level evidence a missing task can be wrongly blamed on the trigger.
D:Configure the correct record-based flow trigger and conditions for the target table. This primarily addresses Flow Designer record trigger, not the specific Flow execution logs and troubleshooting decision. Here, execution history and logs support diagnosis beyond assuming the flow ran.
Question 797
An employee needs an explicit Create entry for the application table. Select TWO statements that correctly combine the New-record module entry point method with evidence or its governing principle.
- Adjust module active state and order settings in an approved application menu.
- Treat a module for an existing record as a guaranteed new record insertion action.
- The eligible user reaches a new record form of the correct table.
- Apply appropriate menu and module role restrictions and independently enforce data ACLs.
- Configure a module that opens the appropriate new-record form.
Explanation
Correct Answers
C:The eligible user reaches a new record form of the correct table. This is directly observable validation of the New-record module entry point result.
E:Configure a module that opens the appropriate new-record form. This is the intended action for New-record module entry point.
Incorrect Answers
A:Adjust module active state and order settings in an approved application menu. This serves the different Active state and module ordering objective, not the selected New-record module entry point plan. Modules can provide distinct navigation actions for creating versus listing records.
B:Treat a module for an existing record as a guaranteed new record insertion action. This is not part of a safe or effective New-record module entry point design. A list-only link may not meet a required direct creation path.
D:Apply appropriate menu and module role restrictions and independently enforce data ACLs. This serves the different Module and menu role visibility objective, not the selected New-record module entry point plan. Modules can provide distinct navigation actions for creating versus listing records.
Question 798
An external integration reads public fields but should not see employee compensation. Testing exposes this failure: Hiding a field in a form view does not prevent direct API reads. Which remediation should be applied FIRST?
- Use the platform's Access Control Debug tools and user impersonation where authorized.
- Assume removing salary from one form view encrypts it from every integration.
- Set field-level ACLs and verify results with actual low-privilege requests.
- Add a carefully scoped ACL script with an explicit boolean outcome for authorized identity.
Explanation
Correct Answer
C:Set field-level ACLs and verify results with actual low-privilege requests. Confirmation requires seeing that a field query returns permitted columns and denies restricted field access.
Incorrect Answers
A:Use the platform's Access Control Debug tools and user impersonation where authorized. It addresses Access Control Debug and denial analysis, not the diagnosed Field-level ACL for sensitive data failure. Hiding a field in a form view does not prevent direct API reads.
B:Assume removing salary from one form view encrypts it from every integration. This retains the Field-level ACL for sensitive data problem. Table ACLs and field ACLs can both affect whether sensitive data is revealed.
D:Add a carefully scoped ACL script with an explicit boolean outcome for authorized identity. It addresses Scripted ACL conditional check, not the diagnosed Field-level ACL for sensitive data failure. Hiding a field in a form view does not prevent direct API reads.
Question 799
A saved loan needs a related audit record created after insert. If the relevant After Business Rule related records safeguard is omitted, which outcome is the MOST directly associated failure?
- Relying on a hidden producer alone cannot block direct API record creation.
- Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail.
- Placing required pre-save validation only in a post-commit notification is too late.
- Copying sensitive hidden server data into a client scratchpad can disclose it.
Explanation
Correct Answer
B:Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail. After rules run after database operations and can react to persisted changes. The corrective approach is to verify after-rule conditions and idempotent related record creation.
Incorrect Answers
A:Relying on a hidden producer alone cannot block direct API record creation. This failure pattern belongs chiefly to Record producer access and audience; it is not the failure most directly tested in the After Business Rule related records situation. Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail.
C:Placing required pre-save validation only in a post-commit notification is too late. This failure pattern belongs chiefly to Before Business Rule validation; it is not the failure most directly tested in the After Business Rule related records situation. Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail.
D:Copying sensitive hidden server data into a client scratchpad can disclose it. This failure pattern belongs chiefly to Display Business Rule and g_scratchpad; it is not the failure most directly tested in the After Business Rule related records situation. Using an inappropriate before-rule dependency on a not-yet-saved sys_id can fail.
Question 800
A server utility reads a configurable app threshold that administrators can adjust. Which approach BEST meets the requirement while respecting the system constraints?
- Read gs.getUserID in server-side script where the effective user identity is required.
- Use a documented server-side GlideSystem role check such as gs.hasRole with the intended role.
- Treat every property value as authenticated proof that the user has the required role.
- Read the app-specific property through gs.getProperty with an appropriate default.
Explanation
Correct Answer
D:Read the app-specific property through gs.getProperty with an appropriate default. GlideSystem can access system property values for server-side configuration. Verification should demonstrate that behavior follows the documented property after a controlled update.
Incorrect Answers
A:Read gs.getUserID in server-side script where the effective user identity is required. This primarily addresses gs.getUserID for current identity, not the specific gs.getProperty server configuration decision. Here, glideSystem can access system property values for server-side configuration.
B:Use a documented server-side GlideSystem role check such as gs.hasRole with the intended role. This primarily addresses gs.hasRole server authorization, not the specific gs.getProperty server configuration decision. Here, glideSystem can access system property values for server-side configuration.
C:Treat every property value as authenticated proof that the user has the required role. This is an unsafe or ineffective shortcut for gs.getProperty server configuration. Putting access-control decisions solely in a user-editable property can create bypasses.
