Question 780
A customer challenges the design after observing: An analytics archive has no provenance or retention controls. Which concept explains the risk?
Explanation
Correct Answer
The described symptoms are explained by: Massive storage scale does not remove privacy and compliance requirements. A supported corrective step is: Set object lifecycle security and governance policies. The closing evidence is: Retention and access tests enforce policy.
Incorrect Answers
That alternative could help with the separate condition: AI compute stays on-premises but data crosses a limited WAN every epoch. It would be checked by training throughput and transfer expense meet limits. For the described case, the necessary correction is set object lifecycle security and governance policies.
This choice concerns Data growth, analytics and AI storage, for example: An AI pipeline expects millisecond restore from a slow retrieval tier. The current storage issue instead hinges on massive storage scale does not remove privacy and compliance requirements. The appropriate evidence is retention and access tests enforce policy.
Although this option is reasonable for 'A data lake lists billions of objects too slowly for analytics.', it is not the specific dependency in the stem. Its action is test namespace indexing and object listing behavior at scale. The stem is resolved more directly by set object lifecycle security and governance policies.