Question 690
A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. A hosted ServiceNow service does not absolve customers of properly configured roles, ACLs and data handling; platform hosting and customer configuration are different responsibilities. The appropriate response is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.
Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. A hosted ServiceNow service does not absolve customers of properly configured roles, ACLs and data handling; platform hosting and customer configuration are different responsibilities. Verify prerequisites with: Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.
Incorrect Answers
Define approved classification, retention and access rules for tenant-managed information before storing sensitive fields in ServiceNow applications or integrating them externally. This step may apply to Tenant data handling and retention governance but is not one of the complementary requirements in this case. The intended pair is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Together with: Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.
Inspect privileged user accounts, change history, service account scope, access review dates, security log signals and relevant 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: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Together with: Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.
The authorized operator reaches the same intended record in the correct working interface with the expected controls and permissions. This step may apply to Unified navigation between workspaces and platform views but is not one of the complementary requirements in this case. The intended pair is: Use the platform shared responsibility model to distinguish vendor-hosted infrastructure controls from customer-managed identity, access, data configuration and application governance. Together with: Inspect the applicable responsibility matrix, instance subscription, tenant roles, configured ACLs, integration data flow and vendor documentation. Scenario: A service owner blames the hosting provider for an overly broad ACL created by the customer's scoped application.


