Question 380
A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. The appropriate response is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.
Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Customer data governance and classification continue to apply in a SaaS platform; interface hiding or assumed default encryption is not an authorization policy. Verify prerequisites with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.
Incorrect Answers
The dashboard shows understandable and timely metrics to authorized viewers without revealing fields they cannot read. This step may apply to Dashboards and Platform Analytics audience permissions but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.
Maintain auditable ownership and periodic review of privileged ServiceNow configuration and integration operations, including shared credentials, emergency elevation and change approvals. This step may apply to Audit and accountability for privileged instance operations but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.
Inspect completeness rules, orphaned relationships, stale discovery timestamps, duplicate identity signals and source ownership. This step may apply to CMDB health completeness correctness and relationship audits but is not one of the complementary requirements in this case. The intended pair is: Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. Together with: Inspect record type, classification, access criteria, encryption options, retention requirement, outbound integration and auditability. Scenario: A security team deletes records to reduce storage but overlooks a legally required retention period and downstream archive.


