Exam CAS-004 topic 1 question 311 discussion

Considerations: - Immutability can be applied to individual files, not the whole blob storage. - Backup verification can be automated for both options. Soft Delete (C): - More efficient and cost-effective for organizations where data compliance requirements are less stringent and data needs to be deleted promptly after backups. - Operational flexibility allows for restoring files without high storage costs. Immutable Blob (D): - More efficient for environments requiring strict data retention and protection from tampering or deletion. - Ensures compliance with strict regulatory requirements, but at a higher cost.

C. Implement soft delete for blobs Here's why: Soft delete allows blobs to be deleted, but they are retained in a deleted state for a specified period. This gives the backup process time to complete before the blobs are permanently deleted. Mirroring would not prevent premature deletion, as both copies would be deleted simultaneously. Fast recovery is a feature that enables faster recovery of deleted blobs, but it doesn't prevent premature deletion. Making blobs immutable would prevent them from being deleted at all, which wouldn't allow for occasional deletions. Therefore, implementing soft delete provides the flexibility to allow occasional deletions while ensuring that backups are completed first, effectively addressing the company's requirement.

ANS C NOT D here is why: Soft delete for blobs: This feature allows you to recover blobs that have been deleted within a specified retention period. When soft delete is enabled, deleted blobs are retained in a "soft deleted" state for a configurable retention period, allowing recovery if necessary. This ensures that even if blobs are deleted prematurely, they can still be restored if needed, thereby providing a safeguard against accidental or premature deletions before backups are completed. However, setting blobs as immutable means that they cannot be modified or deleted for a specified retention period. While this ensures that blobs cannot be deleted or altered during the retention period, it might be too restrictive if you need occasional deletions and could complicate your data management and lifecycle policies.

D. setting the policy according to the backup timestamp.

we don't want to make it immutable, then nothing can be added to it. soft delete is the best option

C. Implement soft delete for blobs: Soft delete is a feature that retains deleted blobs for a specified period of time, allowing for the recovery of blob data that was deleted either unintentionally or maliciously. With soft delete enabled, if a blob is deleted before a backup can take place, it can be recovered from the soft delete state. D. Make the blob immutable: Immutability would prevent any changes, including deletion, to the blobs for a specified retention interval. This is good for compliance and ensuring data is not altered or deleted, but it would not allow occasional deletions as required and could interfere with regular operations that require deletion after backup. Considering the requirements, option C. Implement soft delete for blobs is the best solution.

D is wrong

Eh, I said C at first but changed to D. But who knows what CompTIA would mark as correct. https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-storage-overview

read comments below...immutable does not mean it can NEVER be deleted...just during the time period specified.

Anyone answering D needs to re-evaluate their life. Immutable means it can never be deleted.

C. Implement soft delete for blobs.

D doesn't make sense as the blobs are immutable meaning they CANNOT be deleted which goes against one of the requirements where the blobs need to be occasionally deleted. Therefore the best answer is C

While options like mirroring the blobs at a local data center, enabling fast recovery on the storage account, and implementing soft delete for blobs have their own use cases and advantages, they don't directly address the requirement to prevent blobs from being deleted before successful backups. Immutable storage is specifically designed for this purpose.

C. Implement soft delete for blobs. Soft delete is a feature in Azure Blob Storage that allows you to recover deleted blobs or snapshots of blobs. With soft delete enabled, even if a blob is deleted, it can be retained for a specified retention period (e.g., 7 days) before being permanently deleted. This provides an extra layer of data protection and allows for recovery in case of accidental deletions. You can configure soft delete policies to ensure that blobs are only permanently deleted after a successful backup, addressing the issue of premature deletions.

C seems the best to me.

Make the blob immutable: Immutability means that the data cannot be altered or deleted. This solution would completely prevent deletions which might not meet the requirement of "allowing blobs to be deleted occasionally." Given the scenario, the most fitting solution to ensure that blobs are only deleted after a successful backup and to have a safety net for premature deletions would be: C. Implement soft delete for blobs.

Read the question again. They want a recommendation that deletes the blob storage after the backup. Soft delete will protect the data, but could still delete the blob storage before the backup date. Therefore the best answer here is D.