ServiceNow CAD Practice Test 58
Question 570
A team needs priority or state choices that are meaningful and consistent in scripts. An engineer must explain the recommendation for Choice definitions and dependent choices. Which underlying principle is the MOST accurate?
- Choice lists centralize permitted presentation values and mapped internal values.
- After rules run after database operations and can react to persisted changes.
- Removing a field from a form is different from removing the field from the table.
- A visual required flag alone does not necessarily enforce all non-form writes.
Explanation
Correct Answer
A:Choice lists centralize permitted presentation values and mapped internal values. Therefore the implementation decision is to define stable choice values and applicable dependent-choice configuration.
Incorrect Answers
B:Creating choice labels without consistent internal semantics can break filters and rules. After rules run after database operations and can react to persisted changes.
C:Creating choice labels without consistent internal semantics can break filters and rules. This describes the separate Remove fields from view without deleting data mechanism; the present case instead requires Choice definitions and dependent choices.
D:Creating choice labels without consistent internal semantics can break filters and rules. A visual required flag alone does not necessarily enforce all non-form writes.
Question 571
A facilities team wants to replace emailed room requests with tracked approvals and tasks. Which approach BEST meets the requirement while respecting the system constraints?
- Design a scoped Now Platform app with records, roles and workflow for the recurring process.
- Define personas, authenticated roles, record permissions and suitable interface components.
- Keep heavy specialized computation in an appropriate external compute service and integrate results.
- Assume every unrelated business process requires a separately hosted custom web server.
Explanation
Correct Answer
A:Design a scoped Now Platform app with records, roles and workflow for the recurring process. ServiceNow application development suits record-centered business workflows with governed access. Verification should demonstrate that users submit records and reviewers see authorized assignment and approval history.
Incorrect Answers
B:Define personas, authenticated roles, record permissions and suitable interface components. This primarily addresses Experience design and app permissions, not the specific Workflow fit for scoped applications decision. Here, serviceNow application development suits record-centered business workflows with governed access.
C:Keep heavy specialized computation in an appropriate external compute service and integrate results. This primarily addresses Avoid using platform as high-performance compute engine, not the specific Workflow fit for scoped applications decision. Here, serviceNow application development suits record-centered business workflows with governed access.
D:Assume every unrelated business process requires a separately hosted custom web server. This is an unsafe or ineffective shortcut for Workflow fit for scoped applications. Choosing a record-free visualization engine would omit task state and audit trails.
Question 572
A developer wants a documented client API rather than direct DOM manipulation. Testing exposes this failure: Arbitrary DOM selectors can break after platform interface upgrades. Which remediation should be applied FIRST?
- Use an onSubmit client script to provide feedback and return false when invalid.
- Use supported g_form calls and test the targeted UI type.
- Change field values by rewriting platform-generated DOM IDs instead of using g_form.
- Use onChange with checks for isLoading and the relevant old/new value.
Explanation
Correct Answer
B:Use supported g_form calls and test the targeted UI type. Confirmation requires seeing that the form changes the intended field state and remains compatible with supported UI.
Incorrect Answers
A:Use an onSubmit client script to provide feedback and return false when invalid. It addresses onSubmit client script validation, not the diagnosed g_form API for form fields failure. Arbitrary DOM selectors can break after platform interface upgrades.
C:Change field values by rewriting platform-generated DOM IDs instead of using g_form. This retains the g_form API for form fields problem. g_form is the supported client form API in suitable ServiceNow experiences.
D:Use onChange with checks for isLoading and the relevant old/new value. It addresses onChange client script guards, not the diagnosed g_form API for form fields failure. Arbitrary DOM selectors can break after platform interface upgrades.
Question 573
A custom intake producer needs to set a state and normalize an input on creation. After the recommended Producer script for controlled assignment change is implemented, which observation MOST directly verifies that it works?
- The created record contains the correct requester and asset references.
- After submission the user receives an accurate confirmation without extra duplicate records.
- The new record has the intended initial values after submission.
- Invalid desktop submissions are blocked and users receive actionable guidance.
Explanation
Correct Answer
C:The new record has the intended initial values after submission. This directly tests whether the Producer script for controlled assignment goal was met. Producer scripting can set target record fields during record creation.
Incorrect Answers
A:The created record contains the correct requester and asset references. This is evidence about Producer variable mapping, not direct proof of the required Producer script for controlled assignment behavior. The relevant check is that the new record has the intended initial values after submission.
B:After submission the user receives an accurate confirmation without extra duplicate records. This is evidence about Producer post-submission behavior, not direct proof of the required Producer script for controlled assignment behavior. The relevant check is that the new record has the intended initial values after submission.
D:Invalid desktop submissions are blocked and users receive actionable guidance. This is evidence about onSubmit client script validation, not direct proof of the required Producer script for controlled assignment behavior. The relevant check is that the new record has the intended initial values after submission.
Question 574
A flow must avoid duplicate external transactions when an HTTP call is retried. Which practical correction or implementation decision is MOST directly appropriate?
- Correlate requests and check the external transaction before retrying.
- Configure approved authentication and test expiry or rotation behavior.
- Retry a potentially successful write unlimited times whenever the client times out.
- Test valid and invalid bodies against a safe sandbox endpoint.
Explanation
Correct Answer
A:Correlate requests and check the external transaction before retrying. The intended behavior can be checked because repeated tests do not create duplicate external records for the same business operation.
Incorrect Answers
B:Configure approved authentication and test expiry or rotation behavior. This could help REST authentication with stored credentials, but it does not resolve the REST timeout and retry safety case. Network failure does not prove a remote write was never committed.
C:Retry a potentially successful write unlimited times whenever the client times out. This would not correct the REST timeout and retry safety workflow. Retrying a non-idempotent POST without a key can create duplicate requests.
D:Test valid and invalid bodies against a safe sandbox endpoint. This could help REST endpoint and payload validation, but it does not resolve the REST timeout and retry safety case. Network failure does not prove a remote write was never committed.
Question 575
A process owner needs failed automation to stop safely and expose an actionable error. Which practical correction or implementation decision is MOST directly appropriate?
- Set the correct trigger operation and test positive and negative records.
- Build and test a parameterized subflow for common logic.
- Retry every external operation indefinitely without recording success or failure.
- Test transient errors and implement idempotent recovery where relevant.
Explanation
Correct Answer
D:Test transient errors and implement idempotent recovery where relevant. The intended behavior can be checked because failed steps leave an inspectable execution record and avoid duplicate side effects.
Incorrect Answers
A:Set the correct trigger operation and test positive and negative records. This could help Flow Designer record trigger, but it does not resolve the Flow action error handling and retry case. Automation must handle action failures rather than treating step initiation as completion.
B:Build and test a parameterized subflow for common logic. This could help Reusable subflow design, but it does not resolve the Flow action error handling and retry case. Automation must handle action failures rather than treating step initiation as completion.
C:Retry every external operation indefinitely without recording success or failure. This would not correct the Flow action error handling and retry workflow. Unbounded retries can create repeated notifications or duplicate records.
Question 576
A team wants to avoid repeated server round trips for data known at form load. Which practical correction or implementation decision is MOST directly appropriate?
- Test before-rule conditions and ensure no unnecessary recursive updates.
- Prepare only allowed initial form context and verify permissions.
- Store credentials in g_scratchpad because users are not meant to inspect browser data.
- Refactor common validation into a named scoped utility with unit tests.
Explanation
Correct Answer
B:Prepare only allowed initial form context and verify permissions. The intended behavior can be checked because an onLoad client script can access the prepared permitted scratchpad value.
Incorrect Answers
A:Test before-rule conditions and ensure no unnecessary recursive updates. This could help Before Business Rule validation, but it does not resolve the Display Business Rule and g_scratchpad case. Display Business Rules can provide server-derived data to client form loading.
C:Store credentials in g_scratchpad because users are not meant to inspect browser data. This would not correct the Display Business Rule and g_scratchpad workflow. Copying sensitive hidden server data into a client scratchpad can disclose it.
D:Refactor common validation into a named scoped utility with unit tests. This could help Script Include utility reuse, but it does not resolve the Display Business Rule and g_scratchpad case. Display Business Rules can provide server-derived data to client form loading.
Question 577
A colleague may edit Flows but must not modify every access control or integration. A reviewer proposes this shortcut: Toggle every delegated permission on for all trainees without role review. Which principle BEST explains why a different solution is needed?
- Source control rights may be assigned separately from general delegated editing.
- Delegated developer entitlements can restrict which app components each user edits.
- Git commits preserve source revisions so reviewers can trace changes.
- Delegation does not eliminate the need for review and test evidence.
Explanation
Correct Answer
B:Delegated developer entitlements can restrict which app components each user edits. The appropriate approach is to assign only required delegated file-type permissions for the application.
Incorrect Answers
A:Source control rights may be assigned separately from general delegated editing. This is about Delegated source-control authorization, not why the proposed File-type-specific delegated permissions shortcut should be rejected. Blanket all-file access undermines separation of duties.
C:Git commits preserve source revisions so reviewers can trace changes. This is about Commit application changes to Git, not why the proposed File-type-specific delegated permissions shortcut should be rejected. Blanket all-file access undermines separation of duties.
D:Delegation does not eliminate the need for review and test evidence. This is about Code review and scoped contribution workflow, not why the proposed File-type-specific delegated permissions shortcut should be rejected. Blanket all-file access undermines separation of duties.
Question 578
A team needs to distinguish visual mandatory indicators from authoritative data rules. Which practical correction or implementation decision is MOST directly appropriate?
- Test reference filtering and enforce the underlying read and write ACLs.
- Configure and test choice conditions including fallback behavior.
- Set a field mandatory only in one desktop view and assume no API can omit it.
- Apply server-side mandatory or validation rules with tested exceptions.
Explanation
Correct Answer
D:Apply server-side mandatory or validation rules with tested exceptions. The intended behavior can be checked because aPI and import attempts missing the identifier are handled according to policy.
Incorrect Answers
A:Test reference filtering and enforce the underlying read and write ACLs. This could help Reference qualifier for valid selections, but it does not resolve the Mandatory field storage versus form rendering case. A visual required flag alone does not necessarily enforce all non-form writes.
B:Configure and test choice conditions including fallback behavior. This could help Choice definitions and dependent choices, but it does not resolve the Mandatory field storage versus form rendering case. A visual required flag alone does not necessarily enforce all non-form writes.
C:Set a field mandatory only in one desktop view and assume no API can omit it. This would not correct the Mandatory field storage versus form rendering workflow. Integrations can bypass client-only mandatory checks and introduce incomplete records.
Question 579
A record owner must match the authenticated caller rather than a displayed name. A reviewer proposes this shortcut: Populate trusted record ownership from a user-supplied arbitrary text field. Which principle BEST explains why a different solution is needed?
- Server-side user identity references are more robust than trusting submitted display names.
- Effective group membership should come from server-side identity rather than form text.
- Feedback methods communicate to the user and are not substitutes for access controls.
- Protected artifact policies are distinct from user ACLs and application scope names.
Explanation
Correct Answer
A:Server-side user identity references are more robust than trusting submitted display names. The appropriate approach is to read gs.getUserID in server-side script where the effective user identity is required.
Incorrect Answers
B:Effective group membership should come from server-side identity rather than form text. This is about gs.getUser().isMemberOf group membership, not why the proposed gs.getUserID for current identity shortcut should be rejected. A client-provided name can be forged or ambiguous.
C:Feedback methods communicate to the user and are not substitutes for access controls. This is about gs.addInfoMessage user feedback, not why the proposed gs.getUserID for current identity shortcut should be rejected. A client-provided name can be forged or ambiguous.
D:Protected artifact policies are distinct from user ACLs and application scope names. This is about Protected application files and distribution, not why the proposed gs.getUserID for current identity shortcut should be rejected. A client-provided name can be forged or ambiguous.
Question 580
Several scheduled scripts share the same eligibility calculation. Which approach BEST meets the requirement while respecting the system constraints?
- Supply documented event parameters when queuing the event and consume them safely.
- Move reusable logic into a scoped utility Script Include and call it from permitted server contexts.
- Depend on a browser client script being present when a background job executes.
- Query only eligible records and mark processed work using a consistent idempotency strategy.
Explanation
Correct Answer
B:Move reusable logic into a scoped utility Script Include and call it from permitted server contexts. Shared Script Includes centralize server business logic for maintainability. Verification should demonstrate that the job and event consumer produce consistent results on the same test records.
Incorrect Answers
A:Supply documented event parameters when queuing the event and consume them safely. This primarily addresses Event parameters for notifications, not the specific Utility Script Include for scheduled jobs decision. Here, shared Script Includes centralize server business logic for maintainability.
C:Depend on a browser client script being present when a background job executes. This is an unsafe or ineffective shortcut for Utility Script Include for scheduled jobs. Copying an algorithm into each event and job makes them drift during fixes.
D:Query only eligible records and mark processed work using a consistent idempotency strategy. This primarily addresses Scheduled job idempotent processing, not the specific Utility Script Include for scheduled jobs decision. Here, shared Script Includes centralize server business logic for maintainability.
