Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location PL
Mob_nav_barsMENU

Microsoft Exam AZ-204 Topic 1 Question 104 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 104
Topic #: 1
[All AZ-204 Questions]

You are developing an application to store business-critical data in Azure Blob storage. The application must meet the following requirements:

* Data must not be modified or deleted for a user-specified interval.

* Data must be protected from overwntes and deletes.

* Data must be written once and allowed to be read many times.

You need to protect the data fen the Azure Blob storage account.

Which two actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer: D, F

by Lonna at Sep 14, 2024, 05:25 PM

Limited Time Offer

25%

Off

Get Premium AZ-204 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Felix
2 months ago
I'm with Roslyn on this one. The blob change feed is overkill. Let's stick to the basics - immutability and retention policy. Get the job done without any fancy bells and whistles.
upvoted 0 times
...
Roslyn
2 months ago
Haha, the blob change feed, really? Are we going to hire a team of ninjas to monitor the change feed 24/7? I think A and F are the way to go, simple and effective.
upvoted 0 times
Elouise
1 months ago
Yeah, A and F sound like a solid plan. No need for ninja monitoring with the blob change feed.
upvoted 0 times
...
Jerry
1 months ago
F) Configure a time-based retention policy for the storage account.
upvoted 0 times
...
Dan
1 months ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...
Alita
2 months ago
Hold on, did they say the data must be protected from overwrites and deletes? In that case, option E, enabling the blob change feed, could be useful too. Just to keep an audit trail, you know?
upvoted 0 times
Goldie
1 months ago
That's a good point! Enabling the blob change feed can help with tracking any changes made to the data.
upvoted 0 times
...
Barney
1 months ago
E) Enable the blob change feed for the storage account.
upvoted 0 times
...
Maryann
2 months ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...
Celestine
2 months ago
I also think we should create an account shared-access signature (SAS) to further protect the data.
upvoted 0 times
...
Tammara
2 months ago
I agree with Vilma. That will help protect the data from being modified or deleted.
upvoted 0 times
...
Carrol
2 months ago
I agree, options A and F are the correct choices. Creating an SAS won't protect the data from modification or deletion, and point-in-time restore is more for disaster recovery, not data immutability.
upvoted 0 times
Paris
26 days ago
Point-in-time restore is more for disaster recovery, not data immutability.
upvoted 0 times
...
Joni
29 days ago
Creating an SAS won't protect the data from modification or deletion.
upvoted 0 times
...
Lorean
1 months ago
I agree, options A and F are the best options for data protection.
upvoted 0 times
...
Teddy
2 months ago
I think A and F are the correct choices.
upvoted 0 times
...
...
Vilma
2 months ago
I think we should enable version-level immutability support for the storage account.
upvoted 0 times
...
Emilio
3 months ago
Enabling version-level immutability and configuring a time-based retention policy seem like the way to go. That should meet the requirements of data protection and WORM (write-once, read-many) storage.
upvoted 0 times
Veronica
2 months ago
F) Configure a time-based retention policy for the storage account.
upvoted 0 times
...
King
2 months ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77