Question 210
A compliance officer assumes blob versioning alone will prevent all deliberate deletions and purge activity. What is missing?
Explanation
Correct Answer
Blob versioning preserves earlier content versions, but on its own does not establish an immutable legal retention obligation or prevent every authorized deletion and subsequent purge. The compliance officer's assumption is therefore too broad. Identify the required period and threat model, then configure supported retention, legal hold or immutability controls where appropriate alongside versioning and relevant delete protection. Test how deletes, version cleanup, lifecycle rules and elevated operators behave under those controls. A historical copy might help recovery, yet recovery is different from a policy that prevents deliberate destruction during a mandatory preservation period.
Incorrect Answers
Blob versioning can retain older object versions after modifications but does not by itself impose an immutable retention commitment on those versions. Privileged deletion or purge paths may remain available depending on account settings and lifecycle. The compliance officer needs an appropriate immutable retention or legal hold design in addition to versioning, with supported policy scope and authorized deletion governance. Versioning alone cannot satisfy the stated anti-purge objective.
Blob versioning tracks overwrite history distinctly from manually created blob snapshots. The stated constraint is different: versioning is history management, not a blanket immutability or authorization policy.
Retention policy is finite; do not promise restore of data past its expiry. The stated constraint is different: versioning is history management, not a blanket immutability or authorization policy.






Microsoft Azure Administrator (AZ-104) Practice Tests