An organisation is subject to a regulation requiring certain records to be kept for a defined period. How should this affect retention planning?
Select an answer to reveal the explanation.
Short Explanation
Compliance sets a minimum, not a preference. You have to meet or beat the regulatory period for in-scope data, no matter what operations or storage would prefer. It’s the one input you don’t get to negotiate down.
Full Explanation
The correct choice is the one that treats the regulatory period as a floor that the retention policy must meet or exceed for the data in scope, independently of operational preference. Where a regulation covers data the platform holds, the required period is mandatory. Operational convenience and storage cost can extend it but cannot reduce it.
The option saying regulatory periods can be shortened if storage is constrained, provided operations agrees, is incorrect because a storage constraint is a reason to provision more capacity or narrow what is collected, not to fall short of a legal obligation.
The option saying regulation applies only to application data and never to monitoring telemetry is incorrect because audit logs and some telemetry can fall within regulatory scope, which is why compliance is a named input to retention.
The option saying the shortest period among operational, regulatory and storage considerations should be adopted is incorrect because taking the minimum across the three inverts the logic - operational and regulatory needs set floors while storage sets the ceiling to be provisioned against.
For the exam, treat regulatory retention as a floor and storage capacity as a constraint to plan around.