ServiceNow CSA Practice Test 60
Question 590
An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching. Before changing the configuration, which evidence should the administrator examine FIRST?
- Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results.
- Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions.
- Inspect data source, import staging columns, transform target, field maps, required values, import log and test records.
- Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
Explanation
Correct Answer
A:Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. With coalesce, matching keys can update existing records; absent or ambiguous coalesce fields can create new rows or update an unintended first match. The appropriate response is: Configure coalesce using fields that uniquely identify a target record and validate existing-match behavior before importing updates into production. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.
Incorrect Answers
B:Inspect published article version, valid-to date, review owner, linked attachments, feedback, and access conditions. This evidence is relevant to Knowledge article review, validity and version lifecycle, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.
C:Inspect data source, import staging columns, transform target, field maps, required values, import log and test records. This evidence is relevant to Import set staging and transform-map field mappings, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.
D:Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. This evidence is relevant to Audit and accountability for privileged instance operations, not the most diagnostic first check for this failure. Examine: Inspect source key quality, target uniqueness/indexes, field-map coalesce selections, blank values and transform preview results. Scenario: An import includes empty employee IDs and the administrator never checks whether empty coalesce fields could cause unwanted matching.
Question 591
A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
- Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights.
- Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design.
- The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently.
- Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases.
- Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation.
Explanation
Correct Answers
A:Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. Flow execution identity and action permissions affect outcomes; rerunning as an administrator may hide missing delegation rather than fix it. Verify prerequisites with: Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. Scenario: A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access.
B:Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. Flow execution identity and action permissions affect outcomes; rerunning as an administrator may hide missing delegation rather than fix it. The appropriate response is: Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. Scenario: A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access.
Incorrect Answers
C:The child table supports its intended records and inherited fields while independent applications continue using the shared parent table consistently. This step may apply to Table extension and inherited task fields but is not one of the complementary requirements in this case. The intended pair is: Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. Together with: Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. Scenario: A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access.
D:Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. This step may apply to Reusable subflows and defined input output contracts but is not one of the complementary requirements in this case. The intended pair is: Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. Together with: Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. Scenario: A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access.
E:Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation. This step may apply to Workflow Studio trigger and action design but is not one of the complementary requirements in this case. The intended pair is: Diagnose a failing flow using execution details, data pill values and run-as permission context before granting broad administrative rights. Together with: Inspect flow execution steps, failed action, triggering record, run-as user, denied ACL or connection, input/output mappings and retry design. Scenario: A catalog flow runs manually for an admin but fails when executed by a requester with ordinary access.
Question 592
A field is automatically populated when an agent changes a form, but scheduled imports create records without the value. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?
- When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values.
- One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications.
- UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors.
- The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows.
Explanation
Correct Answer
C:UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. A client script can improve the form experience, but server-side Business Rules and policies own logic that must apply without a browser. Scenario: A field is automatically populated when an agent changes a form, but scheduled imports create records without the value.
Incorrect Answers
A:When the condition changes, the intended form fields switch states predictably without erasing legitimate existing values. This result would support UI Policy actions for conditional field behavior, not the specific outcome required in the case. The relevant acceptance test is: UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. Scenario: A field is automatically populated when an agent changes a form, but scheduled imports create records without the value.
B:One legitimate change produces the intended state and bounded side effect without infinite updates or duplicated notifications. This result would support Business Rule recursion and idempotent side effects, not the specific outcome required in the case. The relevant acceptance test is: UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. Scenario: A field is automatically populated when an agent changes a form, but scheduled imports create records without the value.
D:The expected feed completes on schedule with bounded failures and no duplicate production records or accumulating obsolete staging rows. This result would support Scheduled data imports and operational cleanup, not the specific outcome required in the case. The relevant acceptance test is: UI and integration submissions both meet required persisted-data rules while client-side guidance does not silently mask server errors. Scenario: A field is automatically populated when an agent changes a form, but scheduled imports create records without the value.
Question 593
A quarterly access review finds departed employees still members of groups that grant sensitive application roles. Before changing the configuration, which evidence should the administrator examine FIRST?
- Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements.
- Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs.
- Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior.
- Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals.
Explanation
Correct Answer
D:Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. The platform may host audit capabilities, but customers must configure and review appropriate access and business-process controls. The appropriate response is: Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. Scenario: A quarterly access review finds departed employees still members of groups that grant sensitive application roles.
Incorrect Answers
A:Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This evidence is relevant to Table extension and inherited task fields, not the most diagnostic first check for this failure. Examine: Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. Scenario: A quarterly access review finds departed employees still members of groups that grant sensitive application roles.
B:Inspect table, operation, condition, when timing, current/previous state, affected records and execution logs. This evidence is relevant to Business Rule timing and before after async display behavior, not the most diagnostic first check for this failure. Examine: Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. Scenario: A quarterly access review finds departed employees still members of groups that grant sensitive application roles.
C:Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. This evidence is relevant to Dictionary overrides on extended tables, not the most diagnostic first check for this failure. Examine: Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant approvals. Scenario: A quarterly access review finds departed employees still members of groups that grant sensitive application roles.
Question 594
A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role. Before changing the configuration, which evidence should the administrator examine FIRST?
- Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions.
- Inspect ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results.
- Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context.
- Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI.
Explanation
Correct Answer
A:Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Roles control capabilities while groups often organize work and confer roles; assignment to a task group does not inherently grant all administrator privileges. The appropriate response is: Grant required platform roles through appropriate user/group assignments, validate inherited membership, and avoid assigning admin simply to make one application button visible. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.
Incorrect Answers
B:Inspect ACL debug output, user impersonation context, role requirements, matching table/field rules, condition evaluation and script results. This evidence is relevant to ACL debugging of roles conditions and scripts, not the most diagnostic first check for this failure. Examine: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.
C:Inspect ACL operation, object/table name, field ACL, inherited ACL matching, required roles, scripts, and tested user context. This evidence is relevant to Table-level versus field-level access controls, not the most diagnostic first check for this failure. Examine: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.
D:Inspect entry paths (form, API, import), condition semantics, data policy/ACL coverage, and records written without the browser UI. This evidence is relevant to UI Policy versus server-side data enforcement, not the most diagnostic first check for this failure. Examine: Inspect user record, group memberships, explicit/inherited roles, role delegation policy, session state and required task functions. Scenario: A new service desk agent cannot update assigned incidents and the supervisor proposes adding the admin role.
Question 595
A list row opens the wrong task because an operator copied a display label rather than the underlying record identity. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?
- The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step.
- The dashboard shows understandable and timely metrics to authorized viewers without revealing fields they cannot read.
- The record form shows only legitimately related child records, with unchanged link integrity when a child is edited.
- A selected record can be traced unambiguously from list to form and only its intended fields change after saving.
Explanation
Correct Answer
D:A selected record can be traced unambiguously from list to form and only its intended fields change after saving. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
Incorrect Answers
A:The authorized workflow completes with least-privilege access and failure runs retain a clear cause and safe recovery step. This result would support Workflow Studio debugging and Run As privileges, not the specific outcome required in the case. The relevant acceptance test is: A selected record can be traced unambiguously from list to form and only its intended fields change after saving. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
B:The dashboard shows understandable and timely metrics to authorized viewers without revealing fields they cannot read. This result would support Dashboards and Platform Analytics audience permissions, not the specific outcome required in the case. The relevant acceptance test is: A selected record can be traced unambiguously from list to form and only its intended fields change after saving. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
C:The record form shows only legitimately related child records, with unchanged link integrity when a child is edited. This result would support Related lists and record relationships, not the specific outcome required in the case. The relevant acceptance test is: A selected record can be traced unambiguously from list to form and only its intended fields change after saving. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
Question 596
A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
- Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior.
- Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns.
- Load external data into an import set staging table and use a reviewed transform map for mapping to a target table, checking row errors rather than inserting directly into arbitrary production tables.
- The script reads or changes only intended records with approved permission boundaries and predictable performance.
- Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed.
Explanation
Correct Answers
B:Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. Scheduled imports require data quality, monitoring and cleanup as well as a timer; large or overlapping batches can harm platform performance. The appropriate response is: Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.
E:Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. Scheduled imports require data quality, monitoring and cleanup as well as a timer; large or overlapping batches can harm platform performance. Verify prerequisites with: Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.
Incorrect Answers
A:Inspect parent dictionary settings, child table overrides, required state mapping, target users and integration behavior. This step may apply to Dictionary overrides on extended tables but is not one of the complementary requirements in this case. The intended pair is: Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. Together with: Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.
C:Load external data into an import set staging table and use a reviewed transform map for mapping to a target table, checking row errors rather than inserting directly into arbitrary production tables. This step may apply to Import set staging and transform-map field mappings but is not one of the complementary requirements in this case. The intended pair is: Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. Together with: Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.
D:The script reads or changes only intended records with approved permission boundaries and predictable performance. This step may apply to GlideRecord server-side query and secure result handling but is not one of the complementary requirements in this case. The intended pair is: Run scheduled data imports with explicit source authorization, ingestion monitoring and staging cleanup; prevent large overlapping imports or reprocessing the same unverified feed. Together with: Inspect data source credentials, schedule, last import run, transform errors, volume, retention configuration and duplicate patterns. Scenario: A nightly HR feed succeeds for weeks but old import set rows grow without cleanup and slow instance maintenance.
Question 597
An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
- Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout.
- Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience.
- Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions.
- The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person.
- Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference.
Explanation
Correct Answers
A:Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. Workspace experience and traditional platform form views can differ in component layout and configuration, even when they operate on shared records. Verify prerequisites with: Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. Scenario: An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls.
C:Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. Workspace experience and traditional platform form views can differ in component layout and configuration, even when they operate on shared records. The appropriate response is: Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. Scenario: An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls.
Incorrect Answers
B:Review the target instance, application scope, table records, user roles, intended workflow, and the modules exposed to each audience. This step may apply to Now Platform shared records and configurable applications but is not one of the complementary requirements in this case. The intended pair is: Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. Together with: Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. Scenario: An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls.
D:The task appears in the intended group's queue and in an individual's work only when it is actually assigned to that person. This step may apply to Task assignment group versus individual responsibility but is not one of the complementary requirements in this case. The intended pair is: Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. Together with: Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. Scenario: An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls.
E:Use Next Experience unified navigation and the All menu to locate an application or module, then optionally bookmark commonly used destinations through Favorites rather than changing global module configuration for one user's preference. This step may apply to Next Experience application navigation and favorites but is not one of the complementary requirements in this case. The intended pair is: Choose the appropriate ServiceNow workspace or platform UI for the user's task and verify view/context selection rather than assuming a classic form and a configured workspace always render the same layout. Together with: Inspect workspace route, active record, view name, workspace configuration, user role, and available UI actions. Scenario: An agent receives a training screenshot of a classic form but their landing page opens a Configurable Workspace with different controls.
Question 598
An agent is removed from a group but a scheduled assignment rule still routes new work to that user. Before changing the configuration, which evidence should the administrator examine FIRST?
- Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
- Review task table, assignment group, assigned user, group membership, reassignment audit, and current state.
- Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling.
- Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation.
Explanation
Correct Answer
B:Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. A task assigned to a group but not an individual is group work, not proof any specific agent owns it. The appropriate response is: Assign task records using supported Assignment group and Assigned to semantics, checking group membership and the task state before claiming someone owns the work. Scenario: An agent is removed from a group but a scheduled assignment rule still routes new work to that user.
Incorrect Answers
A:Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. This evidence is relevant to Form sections and related layout configuration, not the most diagnostic first check for this failure. Examine: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: An agent is removed from a group but a scheduled assignment rule still routes new work to that user.
C:Inspect indicator source, collection cadence, historical baselines, aggregation definition, filter changes and denominator handling. This evidence is relevant to Trend indicators versus transactional reports, not the most diagnostic first check for this failure. Examine: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: An agent is removed from a group but a scheduled assignment rule still routes new work to that user.
D:Inspect approval record generation, approver resolution, flow wait state, timeout handling, rejection branches and downstream task creation. This evidence is relevant to Flow approvals and wait-for-condition boundaries, not the most diagnostic first check for this failure. Examine: Review task table, assignment group, assigned user, group membership, reassignment audit, and current state. Scenario: An agent is removed from a group but a scheduled assignment rule still routes new work to that user.
Question 599
An incident editor has the correct role but cannot update Priority when a scripted ACL condition rejects the row. Which result BEST demonstrates that the intended configuration or workflow is operating correctly?
- The intended child table applies the approved override while parent and sibling task forms preserve their current behavior.
- The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval.
- The designated user performs only approved duties, and a nonmember account cannot access the restricted management action.
- A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked.
Explanation
Correct Answer
D:A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. An ACL may require multiple matching elements to pass; a user possessing one listed role does not guarantee an ACL condition or script will pass. Scenario: An incident editor has the correct role but cannot update Priority when a scripted ACL condition rejects the row.
Incorrect Answers
A:The intended child table applies the approved override while parent and sibling task forms preserve their current behavior. This result would support Dictionary overrides on extended tables, not the specific outcome required in the case. The relevant acceptance test is: A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. Scenario: An incident editor has the correct role but cannot update Priority when a scripted ACL condition rejects the row.
B:The flow resumes on an actual authorized decision and never treats an emailed invitation as an approval. This result would support Flow approvals and wait-for-condition boundaries, not the specific outcome required in the case. The relevant acceptance test is: A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. Scenario: An incident editor has the correct role but cannot update Priority when a scripted ACL condition rejects the row.
C:The designated user performs only approved duties, and a nonmember account cannot access the restricted management action. This result would support User group and role assignment principle of least privilege, not the specific outcome required in the case. The relevant acceptance test is: A narrowly scoped ACL correction restores the approved action while lower-privilege test users remain blocked. Scenario: An incident editor has the correct role but cannot update Priority when a scripted ACL condition rejects the row.
Question 600
A list row opens the wrong task because an operator copied a display label rather than the underlying record identity. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
- A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data.
- Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating.
- Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior.
- Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records.
- Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references.
Explanation
Correct Answers
B:Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. The appropriate response is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
E:Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Visible record numbers and display strings help users find records, while sys_id is the stable internal record identifier. Verify prerequisites with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
Incorrect Answers
A:A user with appropriate access sees metrics reflecting the intended filtered records and cannot use the chart to reveal restricted data. This step may apply to Platform analytics as a reporting capability but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
C:Inspect existing form sections, section order, effective form view, field presence and related UI policy behavior. This step may apply to Form sections and related layout configuration but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.
D:Configure or use related lists to display records linked by a supported relationship, checking the reference field and target permissions instead of duplicating child records. This step may apply to Related lists and record relationships but is not one of the complementary requirements in this case. The intended pair is: Use a list to inspect multiple table records and a form to inspect or edit one record identified by its sys_id, distinguishing labels and display values from stored references. Together with: Inspect target table, sys_id, number/display value, reference target, selected view, and audit changes before updating. Scenario: A list row opens the wrong task because an operator copied a display label rather than the underlying record identity.