ServiceNow CAD Practice Test 28
Question 270
A user opens a case form and should see a contextual introductory message. After the recommended onLoad client script initialization change is implemented, which observation MOST directly verifies that it works?
- The created record contains the correct requester and asset references.
- The script responds to deliberate field changes without duplicate startup actions.
- Invalid desktop submissions are blocked and users receive actionable guidance.
- The message or supported field state appears when the form loads.
Explanation
Correct Answer
D:The message or supported field state appears when the form loads. This directly tests whether the onLoad client script initialization goal was met. onLoad scripts execute during form initialization, distinct from onChange or submit events.
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 onLoad client script initialization behavior. The relevant check is that the message or supported field state appears when the form loads.
B:The script responds to deliberate field changes without duplicate startup actions. This is evidence about onChange client script guards, not direct proof of the required onLoad client script initialization behavior. The relevant check is that the message or supported field state appears when the form loads.
C:Invalid desktop submissions are blocked and users receive actionable guidance. This is evidence about onSubmit client script validation, not direct proof of the required onLoad client script initialization behavior. The relevant check is that the message or supported field state appears when the form loads.
Question 271
An app has a general record list and a restricted review module. Which approach BEST meets the requirement while respecting the system constraints?
- Impersonate authorized and unauthorized test users and exercise supported record operations.
- Create suitable application roles and assign them to intended groups or users.
- Give everyone access to sensitive navigation because a table is in a scoped application.
- Assign appropriate Roles to each sensitive module and keep underlying ACLs.
Explanation
Correct Answer
D:Assign appropriate Roles to each sensitive module and keep underlying ACLs. Modules may have narrower navigation roles than the application menu as a whole. Verification should demonstrate that authorized reviewers reach the review module while unrelated users cannot retrieve its records.
Incorrect Answers
A:Impersonate authorized and unauthorized test users and exercise supported record operations. This primarily addresses Impersonation for end-user testing, not the specific Module-specific role requirements decision. Here, modules may have narrower navigation roles than the application menu as a whole.
B:Create suitable application roles and assign them to intended groups or users. This primarily addresses Application role assignment model, not the specific Module-specific role requirements decision. Here, modules may have narrower navigation roles than the application menu as a whole.
C:Give everyone access to sensitive navigation because a table is in a scoped application. This is an unsafe or ineffective shortcut for Module-specific role requirements. A broadly visible sensitive module increases confusion and disclosure risk.
Question 272
A form should let users select a fixed priority category with stable internal values. Which practical correction or implementation decision is MOST directly appropriate?
- Verify parent suitability and test inherited behavior before deploying.
- Use every free-text spelling of approved as a distinct internal state.
- Define and test an appropriate identifier and constraints for lookup workflows.
- Standardize the choice dictionary and test selection-dependent logic.
Explanation
Correct Answer
D:Standardize the choice dictionary and test selection-dependent logic. The intended behavior can be checked because stored choice values remain consistent across forms, reports and scripts.
Incorrect Answers
A:Verify parent suitability and test inherited behavior before deploying. This could help Table extension and inherited fields, but it does not resolve the Choice field value and label case. Choice lists bound selectable values while presenting readable labels.
B:Use every free-text spelling of approved as a distinct internal state. This would not correct the Choice field value and label workflow. Uncontrolled status strings cause inconsistent filtering and automation.
C:Define and test an appropriate identifier and constraints for lookup workflows. This could help Unique business identifier and indexes, but it does not resolve the Choice field value and label case. Choice lists bound selectable values while presenting readable labels.
Question 273
A legitimate requester is unexpectedly denied access to a field despite holding the expected role. After the recommended Access Control Debug and denial analysis change is implemented, which observation MOST directly verifies that it works?
- Debug evidence identifies the relevant rule and failing role or condition.
- Matching users can read and nonmatching users are rejected in impersonation tests.
- A properly privileged administrator can edit controlled ACLs with a recorded change.
- Positive and negative membership tests reflect the caller's assigned group relationships.
Explanation
Correct Answer
A:Debug evidence identifies the relevant rule and failing role or condition. This directly tests whether the Access Control Debug and denial analysis goal was met. Debugging ACL evaluation is more reliable than guessing from form visibility.
Incorrect Answers
B:Matching users can read and nonmatching users are rejected in impersonation tests. This is evidence about Scripted ACL conditional check, not direct proof of the required Access Control Debug and denial analysis behavior. The relevant check is that debug evidence identifies the relevant rule and failing role or condition.
C:A properly privileged administrator can edit controlled ACLs with a recorded change. This is evidence about Elevated security_admin privilege for ACL edits, not direct proof of the required Access Control Debug and denial analysis behavior. The relevant check is that debug evidence identifies the relevant rule and failing role or condition.
D:Positive and negative membership tests reflect the caller's assigned group relationships. This is evidence about gs.getUser().isMemberOf group membership, not direct proof of the required Access Control Debug and denial analysis behavior. The relevant check is that debug evidence identifies the relevant rule and failing role or condition.
Question 274
An administrator wants to declutter a form while preserving reports. An engineer must explain the recommendation for Remove fields from view without deleting data. Which underlying principle is the MOST accurate?
- Reference qualifiers constrain selectable reference candidates, not core database permissions.
- A visual required flag alone does not necessarily enforce all non-form writes.
- Removing a field from a form is different from removing the field from the table.
- Record producer completion is a user workflow that should report the actual created target.
Explanation
Correct Answer
C:Removing a field from a form is different from removing the field from the table. Therefore the implementation decision is to remove the field from the relevant form view rather than deleting its dictionary definition.
Incorrect Answers
A:Deleting a dictionary field can affect retained data and dependent business logic. Reference qualifiers constrain selectable reference candidates, not core database permissions.
B:Deleting a dictionary field can affect retained data and dependent business logic. A visual required flag alone does not necessarily enforce all non-form writes.
D:Deleting a dictionary field can affect retained data and dependent business logic. This describes the separate Producer post-submission behavior mechanism; the present case instead requires Remove fields from view without deleting data.
Question 275
A team wants to test record producer behavior after successful submission. Which practical correction or implementation decision is MOST directly appropriate?
- Test both catalog availability and server-side target ACL controls.
- Confirm target record creation before presenting the completed state.
- Display an order-complete message without checking whether the target record was created.
- Test variable-to-field mapping and type conversion on creation.
Explanation
Correct Answer
B:Confirm target record creation before presenting the completed state. The intended behavior can be checked because after submission the user receives an accurate confirmation without extra duplicate records.
Incorrect Answers
A:Test both catalog availability and server-side target ACL controls. This could help Record producer access and audience, but it does not resolve the Producer post-submission behavior case. Record producer completion is a user workflow that should report the actual created target.
C:Display an order-complete message without checking whether the target record was created. This would not correct the Producer post-submission behavior workflow. A misleading success message can hide a failed write or create duplicate retries.
D:Test variable-to-field mapping and type conversion on creation. This could help Producer variable mapping, but it does not resolve the Producer post-submission behavior case. Record producer completion is a user workflow that should report the actual created target.
Question 276
A form should stop submission when a user has not confirmed a required business declaration. Which approach BEST meets the requirement while respecting the system constraints?
- Use documented g_form methods suited to the field and client context.
- Assume returning true from onSubmit denies every invalid save.
- Use an onSubmit client script to provide feedback and return false when invalid.
- Use an onLoad client script and supported g_form methods for initial presentation.
Explanation
Correct Answer
C:Use an onSubmit client script to provide feedback and return false when invalid. onSubmit scripts run in the client before the form is submitted. Verification should demonstrate that invalid desktop submissions are blocked and users receive actionable guidance.
Incorrect Answers
A:Use documented g_form methods suited to the field and client context. This primarily addresses g_form API for form fields, not the specific onSubmit client script validation decision. Here, onSubmit scripts run in the client before the form is submitted.
B:Assume returning true from onSubmit denies every invalid save. This is an unsafe or ineffective shortcut for onSubmit client script validation. Browser validation cannot replace secure server-side checks for alternate write channels.
D:Use an onLoad client script and supported g_form methods for initial presentation. This primarily addresses onLoad client script initialization, not the specific onSubmit client script validation decision. Here, onSubmit scripts run in the client before the form is submitted.
Question 277
A nightly supplier file repeats external asset IDs but should refresh existing records. A reviewer proposes this shortcut: Coalesce on a nonunique description and assume the correct record is always selected. Which principle BEST explains why a different solution is needed?
- Coalesce matches imported values to target rows and chooses update versus insert.
- Network failure does not prove a remote write was never committed.
- Transform Maps determine how import set fields populate target table fields.
- Auto-map assists matching field names but cannot infer every semantic transformation.
Explanation
Correct Answer
A:Coalesce matches imported values to target rows and chooses update versus insert. The appropriate approach is to mark a suitable unique field map as Coalesce and validate key uniqueness.
Incorrect Answers
B:Network failure does not prove a remote write was never committed. This is about REST timeout and retry safety, not why the proposed Coalesce for update versus insert shortcut should be rejected. Without coalesce the same feed may insert duplicate business records.
C:Transform Maps determine how import set fields populate target table fields. This is about Transform map source-to-target mapping, not why the proposed Coalesce for update versus insert shortcut should be rejected. Without coalesce the same feed may insert duplicate business records.
D:Auto-map assists matching field names but cannot infer every semantic transformation. This is about Auto Map Matching Fields limits, not why the proposed Coalesce for update versus insert shortcut should be rejected. Without coalesce the same feed may insert duplicate business records.
Question 278
An application needs testable common server-side logic used by many scripts. Select TWO statements that correctly combine the Script Include utility reuse method with evidence or its governing principle.
- Populate g_scratchpad from a display Business Rule for the supported form experience.
- Encapsulate shared server logic in a scoped Script Include and call it from eligible contexts.
- Insert the full shared function separately into every rule and maintain inconsistent copies.
- Use a before Business Rule in the proper table and operation to validate or adjust current.
- Multiple callers get consistent results with one maintained implementation.
Explanation
Correct Answers
B:Encapsulate shared server logic in a scoped Script Include and call it from eligible contexts. This is the intended action for Script Include utility reuse.
E:Multiple callers get consistent results with one maintained implementation. This is directly observable validation of the Script Include utility reuse result.
Incorrect Answers
A:Populate g_scratchpad from a display Business Rule for the supported form experience. This serves the different Display Business Rule and g_scratchpad objective, not the selected Script Include utility reuse plan. Script Includes support reusable server-side JavaScript rather than copying logic across rules.
C:Insert the full shared function separately into every rule and maintain inconsistent copies. This is not part of a safe or effective Script Include utility reuse design. Duplicate code increases divergence and makes corrections error-prone.
D:Use a before Business Rule in the proper table and operation to validate or adjust current. This serves the different Before Business Rule validation objective, not the selected Script Include utility reuse plan. Script Includes support reusable server-side JavaScript rather than copying logic across rules.
Question 279
A shared utility must be called only through an explicitly exposed cross-scope interface. Which practical correction or implementation decision is MOST directly appropriate?
- Assume a Script Include is public in every scope solely because its name is known.
- Expose the minimum supported interface and verify caller policy.
- Apply least-privileged cross-scope permissions and negative test operations.
- Configure application access and verify cross-scope denial and allowed interfaces.
Explanation
Correct Answer
B:Expose the minimum supported interface and verify caller policy. The intended behavior can be checked because authorized caller contexts invoke the API while unrelated contexts fail.
Incorrect Answers
A:Assume a Script Include is public in every scope solely because its name is known. This would not correct the Script Include accessible from scope setting workflow. Unrestricted cross-scope method calls can bypass planned encapsulation.
C:Apply least-privileged cross-scope permissions and negative test operations. This could help Table application access and CRUD scope, but it does not resolve the Script Include accessible from scope setting case. Cross-scope API exposure should be intentional to protect app boundaries.
D:Configure application access and verify cross-scope denial and allowed interfaces. This could help Private scope protects internal application files, but it does not resolve the Script Include accessible from scope setting case. Cross-scope API exposure should be intentional to protect app boundaries.
Question 280
A flow must send the new case number to a notification step. A reviewer proposes this shortcut: Copy a sample case number as fixed text into every subsequent flow action. Which principle BEST explains why a different solution is needed?
- Ordinary configuration properties should not be assumed suitable for protected secrets.
- Legacy Workflow and Flow Designer coexist in some instances but differ in maintenance and capability.
- Execution history and logs support diagnosis beyond assuming the flow ran.
- Data pills carry typed step and trigger outputs through a flow.
Explanation
Correct Answer
D:Data pills carry typed step and trigger outputs through a flow. The appropriate approach is to map the appropriate trigger and step output data pills into action inputs.
Incorrect Answers
A:Ordinary configuration properties should not be assumed suitable for protected secrets. This is about Properties are not a secret vault, not why the proposed Flow Designer data pills shortcut should be rejected. Hard-coded values can misroute actions when incoming records differ.
B:Legacy Workflow and Flow Designer coexist in some instances but differ in maintenance and capability. This is about Workflow versus Flow Designer lifecycle, not why the proposed Flow Designer data pills shortcut should be rejected. Hard-coded values can misroute actions when incoming records differ.
C:Execution history and logs support diagnosis beyond assuming the flow ran. This is about Flow execution logs and troubleshooting, not why the proposed Flow Designer data pills shortcut should be rejected. Hard-coded values can misroute actions when incoming records differ.
