ServiceNow CAD Practice Test 24
Question 230
A department wants catalog-like questions while storing the result in its application table. Which practical correction or implementation decision is MOST directly appropriate?
- Choose a Record Producer and validate target field mappings.
- Set and validate initial values in the supported producer creation context.
- Test variable-to-field mapping and type conversion on creation.
- Assume every Service Catalog item automatically creates a record in the developer's custom table.
Explanation
Correct Answer
A:Choose a Record Producer and validate target field mappings. The intended behavior can be checked because submitting the producer creates a correctly populated target record.
Incorrect Answers
B:Set and validate initial values in the supported producer creation context. This could help Producer script for controlled assignment, but it does not resolve the Record Producer creates app record case. Record Producers provide a simplified record-creation interface for specified tables.
C:Test variable-to-field mapping and type conversion on creation. This could help Producer variable mapping, but it does not resolve the Record Producer creates app record case. Record Producers provide a simplified record-creation interface for specified tables.
D:Assume every Service Catalog item automatically creates a record in the developer's custom table. This would not correct the Record Producer creates app record workflow. Creating a catalog item alone may produce a request item rather than the intended app record.
Question 231
A process owner needs failed automation to stop safely and expose an actionable error. Select TWO statements that correctly combine the Flow action error handling and retry method with evidence or its governing principle.
- Map the appropriate trigger and step output data pills into action inputs.
- Failed steps leave an inspectable execution record and avoid duplicate side effects.
- Configure supported failure handling, controlled retries and notifications for the flow.
- Retry every external operation indefinitely without recording success or failure.
- Extract shared logic into a subflow with typed inputs and documented outputs.
Explanation
Correct Answers
B:Failed steps leave an inspectable execution record and avoid duplicate side effects. This is directly observable validation of the Flow action error handling and retry result.
C:Configure supported failure handling, controlled retries and notifications for the flow. This is the intended action for Flow action error handling and retry.
Incorrect Answers
A:Map the appropriate trigger and step output data pills into action inputs. This serves the different Flow Designer data pills objective, not the selected Flow action error handling and retry plan. Automation must handle action failures rather than treating step initiation as completion.
D:Retry every external operation indefinitely without recording success or failure. This is not part of a safe or effective Flow action error handling and retry design. Unbounded retries can create repeated notifications or duplicate records.
E:Extract shared logic into a subflow with typed inputs and documented outputs. This serves the different Reusable subflow design objective, not the selected Flow action error handling and retry plan. Automation must handle action failures rather than treating step initiation as completion.
Question 232
Some users need normal case access but must not see administrative functions. Which practical correction or implementation decision is MOST directly appropriate?
- Test both navigation visibility and record security as different users.
- Configure module roles and test table operations under least-privileged accounts.
- Give everyone access to sensitive navigation because a table is in a scoped application.
- Audit effective role memberships for sample users before deployment.
Explanation
Correct Answer
B:Configure module roles and test table operations under least-privileged accounts. The intended behavior can be checked because authorized reviewers reach the review module while unrelated users cannot retrieve its records.
Incorrect Answers
A:Test both navigation visibility and record security as different users. This could help Application menu role restriction, but it does not resolve the Module-specific role requirements case. 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 would not correct the Module-specific role requirements workflow. A broadly visible sensitive module increases confusion and disclosure risk.
D:Audit effective role memberships for sample users before deployment. This could help Role inclusion and effective access, but it does not resolve the Module-specific role requirements case. Modules may have narrower navigation roles than the application menu as a whole.
Question 233
An application owner asks for persistent numeric effort alongside text description. Which practical correction or implementation decision is MOST directly appropriate?
- Use a decorative form label as an indexed persistent field.
- Configure and test choice conditions including fallback behavior.
- Add the appropriate dictionary field and update form design.
- Apply server-side mandatory or validation rules with tested exceptions.
Explanation
Correct Answer
C:Add the appropriate dictionary field and update form design. The intended behavior can be checked because the field persists and is queryable across records and lists.
Incorrect Answers
A:Use a decorative form label as an indexed persistent field. This would not correct the Add fields from the table dictionary workflow. Adding a form annotation does not create a persistent data column.
B:Configure and test choice conditions including fallback behavior. This could help Choice definitions and dependent choices, but it does not resolve the Add fields from the table dictionary case. Table columns hold persisted values while form configuration determines display.
D:Apply server-side mandatory or validation rules with tested exceptions. This could help Mandatory field storage versus form rendering, but it does not resolve the Add fields from the table dictionary case. Table columns hold persisted values while form configuration determines display.
Question 234
An ACL needs both role eligibility and a testable field-based condition. Which practical correction or implementation decision is MOST directly appropriate?
- Define explicit access criteria and test both false and true branches.
- Check only one successful administrative record and assume all other record conditions are correct.
- Define an operation-specific write policy and test record updates.
- Validate scripted ACL behavior for direct record and API requests.
Explanation
Correct Answer
A:Define explicit access criteria and test both false and true branches. The intended behavior can be checked because access tests reflect both role membership and field condition evaluation.
Incorrect Answers
B:Check only one successful administrative record and assume all other record conditions are correct. This would not correct the Access control condition versus role workflow. Granting access based on either unrelated condition alone may bypass intended restrictions.
C:Define an operation-specific write policy and test record updates. This could help Table write operation ACL, but it does not resolve the Access control condition versus role case. ACL role, condition and script gates are evaluated to determine permitted operations.
D:Validate scripted ACL behavior for direct record and API requests. This could help Scripted ACL conditional check, but it does not resolve the Access control condition versus role case. ACL role, condition and script gates are evaluated to determine permitted operations.
Question 235
A form must calculate a permitted derived value before creating a target record. Which practical correction or implementation decision is MOST directly appropriate?
- Set and validate initial values in the supported producer creation context.
- Edit a random unrelated table in the producer script instead of populating its target record.
- Test both catalog availability and server-side target ACL controls.
- Choose a Record Producer and validate target field mappings.
Explanation
Correct Answer
A:Set and validate initial values in the supported producer creation context. The intended behavior can be checked because the new record has the intended initial values after submission.
Incorrect Answers
B:Edit a random unrelated table in the producer script instead of populating its target record. This would not correct the Producer script for controlled assignment workflow. Using arbitrary client-side logic alone cannot guarantee target record invariants.
C: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 script for controlled assignment case. Producer scripting can set target record fields during record creation.
D:Choose a Record Producer and validate target field mappings. This could help Record Producer creates app record, but it does not resolve the Producer script for controlled assignment case. Producer scripting can set target record fields during record creation.
Question 236
A case form contains salary details that ordinary case readers must not access. After the recommended Field-level ACL for sensitive data change is implemented, which observation MOST directly verifies that it works?
- Authorized role reads work while role-negative direct read tests are denied.
- A field query returns permitted columns and denies restricted field access.
- Matching users can read and nonmatching users are rejected in impersonation tests.
- Direct URL and API tests fail for users without the record role.
Explanation
Correct Answer
B:A field query returns permitted columns and denies restricted field access. This directly tests whether the Field-level ACL for sensitive data goal was met. Table ACLs and field ACLs can both affect whether sensitive data is revealed.
Incorrect Answers
A:Authorized role reads work while role-negative direct read tests are denied. This is evidence about Table read access control, not direct proof of the required Field-level ACL for sensitive data behavior. The relevant check is that a field query returns permitted columns and denies restricted field access.
C: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 Field-level ACL for sensitive data behavior. The relevant check is that a field query returns permitted columns and denies restricted field access.
D:Direct URL and API tests fail for users without the record role. This is evidence about Distinguish module access from record roles, not direct proof of the required Field-level ACL for sensitive data behavior. The relevant check is that a field query returns permitted columns and denies restricted field access.
Question 237
A server Business Rule sends email directly with custom code on each state update. Which approach BEST meets the requirement while respecting the system constraints?
- Queue an appropriate event or use supported notifications rather than duplicating email code.
- Configure an inbound email action or supported inbound processing with identity and record matching.
- Copy SMTP credentials into a Business Rule to send mail independently of platform notifications.
- Configure recipients and template variables from permitted record fields.
Explanation
Correct Answer
A:Queue an appropriate event or use supported notifications rather than duplicating email code. Event and notification configuration separates business events from message formatting. Verification should demonstrate that email generation follows the configured notification with separately testable triggers.
Incorrect Answers
B:Configure an inbound email action or supported inbound processing with identity and record matching. This primarily addresses Inbound email action parsing, not the specific Event-driven email versus synchronous code decision. Here, event and notification configuration separates business events from message formatting.
C:Copy SMTP credentials into a Business Rule to send mail independently of platform notifications. This is an unsafe or ineffective shortcut for Event-driven email versus synchronous code. Handcoded email in every rule can produce duplicate sends and poor auditability.
D:Configure recipients and template variables from permitted record fields. This primarily addresses Email recipients and templates, not the specific Event-driven email versus synchronous code decision. Here, event and notification configuration separates business events from message formatting.
Question 238
A Record Producer collects requester and asset details as variables. After the recommended Producer variable mapping change is implemented, which observation MOST directly verifies that it works?
- Invalid entries fail on both form submission and non-form write paths.
- Submitting the producer creates a correctly populated target record.
- The created record contains the correct requester and asset references.
- Eligible users create appropriate records while unauthorized create and read attempts fail.
Explanation
Correct Answer
C:The created record contains the correct requester and asset references. This directly tests whether the Producer variable mapping goal was met. Catalog variables are user inputs that require explicit mapping or producer script logic.
Incorrect Answers
A:Invalid entries fail on both form submission and non-form write paths. This is evidence about Client-side validation versus authoritative enforcement, not direct proof of the required Producer variable mapping behavior. The relevant check is that the created record contains the correct requester and asset references.
B:Submitting the producer creates a correctly populated target record. This is evidence about Record Producer creates app record, not direct proof of the required Producer variable mapping behavior. The relevant check is that the created record contains the correct requester and asset references.
D:Eligible users create appropriate records while unauthorized create and read attempts fail. This is evidence about Record producer access and audience, not direct proof of the required Producer variable mapping behavior. The relevant check is that the created record contains the correct requester and asset references.
Question 239
A code owner wants changes from a ServiceNow application tracked in version control. Select THREE statements that correctly combine the Link app to Git repository in Studio method with evidence or its governing principle.
- The app is linked to the expected repository and committed changes are traceable.
- Configure supported Studio source control integration to the approved remote repository.
- ServiceNow source control integration manages application metadata versions through repository operations.
- Rename the app without configuring repository access and assume it starts committing automatically.
- Commit the appropriate scoped application changes with descriptive revision metadata.
- Use supported source control retrieval or pull operations after reviewing branch and local changes.
Explanation
Correct Answers
A:The app is linked to the expected repository and committed changes are traceable. This is directly observable validation of the Link app to Git repository in Studio result.
B:Configure supported Studio source control integration to the approved remote repository. This is the intended action for Link app to Git repository in Studio.
C:ServiceNow source control integration manages application metadata versions through repository operations. This explains why the implementation and evidence fit together.
Incorrect Answers
D:Rename the app without configuring repository access and assume it starts committing automatically. This is not part of a safe or effective Link app to Git repository in Studio design. Untracked manual editing can produce undocumented deployment drift.
E:Commit the appropriate scoped application changes with descriptive revision metadata. This serves the different Commit application changes to Git objective, not the selected Link app to Git repository in Studio plan. ServiceNow source control integration manages application metadata versions through repository operations.
F:Use supported source control retrieval or pull operations after reviewing branch and local changes. This serves the different Retrieve upstream source changes objective, not the selected Link app to Git repository in Studio plan. ServiceNow source control integration manages application metadata versions through repository operations.
Question 240
A notification must reference the case number in its body. Which practical correction or implementation decision is MOST directly appropriate?
- Validate sender authorization and target record before applying the update.
- Put a real customer's address in a shared template as the global default for every case.
- Review the generated outbound email and correct conditions or transport errors.
- Use approved recipient resolution and validate rendered email content.
Explanation
Correct Answer
D:Use approved recipient resolution and validate rendered email content. The intended behavior can be checked because the test email reaches the expected recipient with accurate reference values.
Incorrect Answers
A:Validate sender authorization and target record before applying the update. This could help Inbound email action parsing, but it does not resolve the Email recipients and templates case. Notification rendering supports record-derived context and configured recipients.
B:Put a real customer's address in a shared template as the global default for every case. This would not correct the Email recipients and templates workflow. Hardcoded recipient strings can route sensitive records to the wrong person.
C:Review the generated outbound email and correct conditions or transport errors. This could help Email delivery troubleshooting, but it does not resolve the Email recipients and templates case. Notification rendering supports record-derived context and configured recipients.
