Question 380
A log-ingestion service writes continually to an Azure append blob using Append Block. Blob versioning is enabled on the account, but compliance expects an automatically generated previous version for every append. What should the administrator explain and recommend?
Explanation
Correct Answer
Microsoft lists Append Block among write operations that do not trigger creation of an automatic blob version. If the business requires a recoverable state after each append, take supported explicit snapshots or implement another separately recorded history mechanism.
Incorrect Answers
Azure Blob versioning does not create a new version for every Append Block operation. Assuming that each append automatically preserves a recoverable pre-append state can leave gaps in the organization’s required history.
Blob versioning can still be enabled for the account and can retain prior versions when eligible write operations occur. The presence of an append blob does not force versioning off for all block blobs in the account.
Setting blob metadata cannot retroactively reconstruct each earlier append state. An additional metadata write changes metadata but does not recreate the historical byte sequences that were never independently captured.