Question 470
An enterprise uses several clouds but alerts cannot be attributed to the correct account owner. What should testing demonstrate before the design is approved?
Explanation
Correct Answer
The acceptance result is an alert routes to the correct application owner using provider-specific identity fields. It validates the design principle that Risk ownership depends on normalized cross-cloud inventory.
Incorrect Answers
The proposed evidence relates to another situation: A cloud security team wants one risk inventory for Azure and AWS compute resources. Integrated posture management requires authenticated provider connections. The architect needs verification that an alert routes to the correct application owner using provider-specific identity fields.
That test would support a different case: A company connects AWS but denies its security connector required role permissions. Connector access must be sufficient for inventory without granting unrestricted control. The present control must instead show that an alert routes to the correct application owner using provider-specific identity fields.
It verifies another security outcome rather than the current risk: A platform team has no way to compare threat protection coverage for cloud VMs and managed databases. Cloud workload protection depends on explicit services, plans, and supported workloads. Here the expected evidence is an alert routes to the correct application owner using provider-specific identity fields.