Question 160
A support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
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 support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.
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 support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.
Incorrect Answers
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 support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.
The enabled application appears in the intended instance with dependencies satisfied and its features tested without breaking existing integrations. This step may apply to Application installation and plugin activation preflight 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 support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.
Inspect VTB board type, source table/filter, lane mapping, card linkage, access permissions, and field update effects. This step may apply to Visual Task Board data-driven and freeform handling 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 support engineer sees the same Caller display name on two incidents and assumes both rows have identical record identities.


