A company hosts a large amount of data in blob storage for its customers. The company recently had a number of issues with this data being prematurely deleted before the scheduled backup processes could be completed. The management team has asked the security architect for a recommendation that allows blobs to be deleted occasionally, but only after a successful backup. Which of the following solutions will BEST meet this requirement?
Implementing soft delete for blobs is the best solution to meet the requirement. Soft delete allows you to recover deleted blobs or snapshots of blobs within a specified retention period. This feature provides an additional layer of protection against premature deletion by ensuring that blobs are not permanently deleted until after a successful backup has been confirmed. Unlike immutability, soft delete does not prevent blobs from being deleted or modified after a specified period, thus allowing for occasional deletions as needed.
read comments below...immutable does not mean it can NEVER be deleted...just during the time period specified.
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.
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.
Immutable means it cannot be deleted, C is the best answer. Similar to how values in an immutable string or array cannot be deleted in coding.
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.
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.
blob immutability does not mean it cannot be deleted read below To make a blob immutable in Azure, you need to configure an immutability policy for the blob. An immutability policy is a rule that prevents the blob from being modified or deleted for a specified period of time. There are two types of immutability policies: time-based retention policies and legal hold policies. A time-based retention policy sets a fixed duration for the immutability of the blob, while a legal hold policy sets an indefinite duration until the policy is cleared D is the best Answer
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.
D. Make the blob immutable. Implementing immutability on the blobs is the best solution to meet the requirement. Immutability ensures that once data is written, it cannot be modified or deleted for a specified period of time. This means that even if someone attempts to delete the blob, it will remain intact until the immutability period expires. This ensures that data will not be prematurely deleted before backups can be completed.
D. setting the policy according to the backup timestamp.
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
Anyone answering D needs to re-evaluate their life. Immutable means it can never be deleted.
I love your confidence... As mentioned below...this is copied from Microsoft's website: Time-based retention policies: With a time-based retention policy, users can set policies to store data for a specified interval. When a time-based retention policy is set, objects can be created and read, but not modified or deleted. After the retention period has expired, objects can be deleted but not overwritten.
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
C seems the best to me.
C. Implement soft delete for blobs. Soft delete is a feature in Azure Blob Storage that allows you to recover blobs or objects that have been deleted accidentally. When soft delete is enabled, blobs are not immediately removed upon deletion but are retained for a specified retention period. During this retention period, you can recover the deleted blobs if needed. This feature ensures that blobs are not prematurely deleted and can be restored if required, which aligns with the requirement of ensuring data is not deleted before a successful backup.
Chat GPT: D. Make the blob immutable. Making the blob immutable means that once it is created, it cannot be modified or deleted for a specified retention period. This ensures that the data is protected from accidental or premature deletion until the retention period expires. It allows you to meet the backup requirement by keeping the data intact until after a successful backup is completed. The other options have their merits but do not directly address the requirement in the same way: A. Mirroring the blobs at a local data center can provide redundancy but doesn't prevent accidental deletions. B. Enabling fast recovery on the storage account may improve recovery times but doesn't prevent deletions before a successful backup. C. Implementing soft delete for blobs can help recover deleted blobs, but it doesn't necessarily prevent premature deletions before a backup is completed. Soft delete is typically used for recovery purposes rather than data retention.
Negative when you ask Chap GBT you need Version 4.0 and tell it to give the comptia answer C. Implement soft delete for blobs. This aligns with general data protection and recovery principles that CompTIA emphasizes in its cybersecurity training and certifications.