Deal of The Day! 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 US
Mob_nav_barsMENU

Microsoft AZ-204 Exam - 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:

0/2000 characters
Submit Cancel
Lezlie
5 months ago
Wait, can you really prevent deletes with just A? Sounds too good to be true.
upvoted 0 times
...
Anthony
5 months ago
Wow, I didn't know about version-level immutability!
upvoted 0 times
...
Graciela
5 months ago
Not sure about C, seems unnecessary here.
upvoted 0 times
...
Derick
5 months ago
I think B is also important for access control.
upvoted 0 times
...
Barrett
6 months ago
Definitely A and F for immutability and retention!
upvoted 0 times
...
Fausto
6 months ago
I vaguely recall that shared-access signatures are more about granting access rather than protecting data, so I’m leaning towards options that focus on immutability and retention.
upvoted 0 times
...
Eleonora
6 months ago
I practiced a similar question where we had to protect data from overwrites. I feel like point-in-time restore might be relevant, but I’m not completely confident.
upvoted 0 times
...
Doug
6 months ago
I think enabling a time-based retention policy could be a good option since it aligns with the requirement to prevent data modification for a specified interval.
upvoted 0 times
...
Bettye
6 months ago
I remember something about immutability in Azure Blob storage, but I'm not entirely sure if version-level immutability is the right choice here.
upvoted 0 times
...
Ezekiel
6 months ago
This is a tricky one. I'm not sure if a service SAS (option D) would be enough to protect the data, since that's more for access control. I think the combination of A and F is the way to go to meet all the stated requirements.
upvoted 0 times
...
Sheron
6 months ago
Okay, I've got this. The requirements clearly call for immutability and data protection. I'd go with A to enable version-level immutability, and F to configure a time-based retention policy. That should cover the key needs.
upvoted 0 times
...
Alex
6 months ago
Hmm, I'm a bit confused. There are a lot of options here and I'm not sure which ones fully address the requirements. I'll need to think through each one carefully to determine the best approach.
upvoted 0 times
...
Ezekiel
7 months ago
This question seems straightforward. I think the key is to focus on the requirements - data must not be modified or deleted, must be protected from overwrites and deletes, and must be write-once read-many. The options that stand out to me are A and F.
upvoted 0 times
...
Leah
7 months ago
I think using Python scripts would be a good choice since they're easily readable and can handle HTTPS for authentication.
upvoted 0 times
...
Felix
2 years 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 years 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 year 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 year ago
F) Configure a time-based retention policy for the storage account.
upvoted 0 times
...
Dan
1 year ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...
Alita
2 years 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 year 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 year ago
E) Enable the blob change feed for the storage account.
upvoted 0 times
...
Maryann
2 years ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...
Celestine
2 years ago
I also think we should create an account shared-access signature (SAS) to further protect the data.
upvoted 0 times
...
Tammara
2 years ago
I agree with Vilma. That will help protect the data from being modified or deleted.
upvoted 0 times
...
Carrol
2 years 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
1 year ago
Point-in-time restore is more for disaster recovery, not data immutability.
upvoted 0 times
...
Joni
1 year ago
Creating an SAS won't protect the data from modification or deletion.
upvoted 0 times
...
Lorean
1 year ago
I agree, options A and F are the best options for data protection.
upvoted 0 times
...
Teddy
2 years ago
I think A and F are the correct choices.
upvoted 0 times
...
...
Vilma
2 years ago
I think we should enable version-level immutability support for the storage account.
upvoted 0 times
...
Emilio
2 years 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 years ago
F) Configure a time-based retention policy for the storage account.
upvoted 0 times
...
King
2 years ago
A) Enable version-level immutability support for the storage account.
upvoted 0 times
...
...

Save Cancel