ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 3 question 83 discussion

Actual exam question from Microsoft's AZ-104
Question #: 83
Topic #: 3
[All AZ-104 Questions]

HOTSPOT
-

You have an Azure Storage account named storage1 that contains two containers named container1 and container2. Blob versioning is enabled for both containers.

You periodically take blob snapshots of critical blobs.

You create the following lifecycle management policy.



For each of the following statements, select Yes if the statement is true. Otherwise, select No.

NOTE: Each correct selection is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer:
by Batiste2023 at Nov. 3, 2023, 8:57 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Batiste2023
Highly Voted 1 year, 7 months ago
Correct, YNN. Y - See section tierToCool N - rule1 only applies to container1, not container2, see section prefixMatch N - This one is a bit complicated. Rehydrated files (that were in the archive tier first and then returned to hot or cool) wouldn't necessarily be archived after 30 days - as there's a condition that the last tier change must be at least 7 days ago. (I'll leave it open how these files became archived in the first place, before 30 days after creation...)
upvoted 27 times
WeepingMaplte
1 year, 2 months ago
First is No. Missing subtype "snapshot": { }, https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/2021-02-01/storageaccounts/managementpolicies?tabs=json&pivots=deployment-language-arm-template#quickstart-templates https://learn.microsoft.com/en-us/answers/questions/1282997/azure-blob-storage-life-cycle-management-not-worki
upvoted 12 times
...
RajeshwaranM
5 months, 3 weeks ago
Correct, NNN. Answer from chat GPT : NNN If it wrong suggest me the answer with microsoft documentaion please A blob snapshot automatically moves to the Cool access tier after 15 days. The policy applies to block blob types with a prefix of container1/. Since blob snapshots are not explicitly mentioned, they are not covered by this rule. Answer: No. A blob version in container2 automatically moves to the Archive access tier after 30 days. The policy applies only to blobs in container1/ (as per the prefixMatch filter). Blobs in container2 are not included in this lifecycle rule. Answer: No. A rehydrated version automatically moves to the Archive access tier after 30 days. There is no mention of rehydrated versions in the lifecycle policy. The policy only applies to transitioning blobs from tierToCool or tierToArchive. Answer: No.
upvoted 2 times
...
MiniLa92
10 months, 4 weeks ago
Third one is No, because daysAfterLastTierChangeGreaterThan is present in policy. Please refer FAQs at https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-faq If there's a lifecycle management policy in effect for the storage account, then rehydrating a blob by changing its tier can result in a scenario where the lifecycle policy moves the blob back to the archive tier. This can happen if the last modified time, creation time, or last access time is beyond the threshold set for the policy. There are three ways to prevent this from happening: Add the daysAfterLastTierChangeGreaterThan condition to the tierToArchive action of the policy. Disable the rule that affects this blob temporarily to prevent it from being archived again. Re-enable the rule when the blob can be safely moved back to archive tier. If the blob needs to stay in the hot, cool, or cold tier permanently, copy the blob to another location where the lifecycle manage policy isn't in effect.
upvoted 4 times
...
Josh219
7 months, 1 week ago
Its NO NO NO Explanation for First: Given that the policy provided does not explicitly mention snapshots or container2, and only applies to blobs within container1, the correct answer to whether blob snapshots automatically move to the Cool access tier after 15 days based on the policy provided is: No.
upvoted 2 times
...
Load full discussion...
...
clg003
Highly Voted 1 year, 6 months ago
NNN There is no snapshot section. Only a version section. So there is no policy defgined for any snapshot not matter which containter its in. The is no policy for container 2 since this one is filtered for only container 1. Hard No. Rehydrated version keep their original creation date and the current rules still apply so if anything it will be less than 30 days.
upvoted 13 times
...
Mitko_V_Milkov
Most Recent 4 months, 3 weeks ago
The answer is NNN. The first question is no because: The policy moves the current version of a blob in container1 to Cool after 15 days. Snapshots are not the current version, so they won't be moved to Cool directly. They will, however, be moved to Archive after 7 days from the last tier change of that specific version (or after 30 days from creation, whichever comes first). Only BlockBlob is mentioned in the policy.
upvoted 2 times
...
Dankho
8 months, 2 weeks ago
a version is a snapshot in time. therefore #1 is yes. YNN final answer bob!
upvoted 1 times
Josh219
7 months, 1 week ago
Explanation for First: Given that the policy provided does not explicitly mention snapshots or container2, and only applies to blobs within container1, the correct answer to whether blob snapshots automatically move to the Cool access tier after 15 days based on the policy provided is: No.
upvoted 1 times
...
Dankho
8 months, 2 weeks ago
correction: A blob snapshot automatically moves to the Cool access tier after 15 days. Answer: No. The policy does not mention snapshots, so this statement is not supported. A blob version in container2 automatically moves to the Archive access tier after 30 days. Answer: No. The policy only applies to container1 as indicated by the prefixMatch filter. A rehydrated version automatically moves to the Archive access tier after 30 days. Answer: Yes. The policy allows for blobs to transition to the Archive tier after 30 days from creation, including rehydrated blobs, as long as they meet the criteria.
upvoted 2 times
...
...
[Removed]
9 months, 3 weeks ago
WRONG No No No
upvoted 2 times
...
certainly
10 months ago
1. A blob snapshot automatically moves to the Cool access tier after 15 days: • Answer: No • Reason: The rule specifies a prefix match for “container1/”. The statement does not specify which container the snapshot belongs to. If it’s not from “container1/”, the rule doesn’t apply. 2. A blob version in container2 automatically moves to the Archive access tier after 30 days: • Answer: No • Reason: The prefix filter only applies to “container1/”. Since the blob is in “container2”, it won’t be moved to the Archive tier. 3. A rehydrated version automatically moves to the Archive access tier after 30 days: • Answer: No • Reason: Again, the rule applies only to blobs in “container1/”. The statement does not specify that the rehydrated version is from “container1/”, so the rule doesn’t apply.
upvoted 3 times
...
a6bd45e
11 months, 1 week ago
Incorrect - NNN N - there is no section defining what to do with snapshots (only versions) N - rule is defined for prefix container1 N - agree with rest of comments.
upvoted 2 times
...
LovelyGroovey
1 year ago
This is what I think. - A blob snapshot automatically moves to the Cool access tier after 15 days. Yes, a blob snapshot automatically moves to the Cool access tier after 15 days according to the provided lifecycle management policy. This policy ensures efficient management of blob snapshots by transitioning them to cooler storage tiers over time. ¯ A blob version in container2 automatically moves to the Archive access tier after 30 days. No, The provided lifecycle management policy does not explicitly state that a blob version in container2 automatically moves to the Archive access tier after 30 days. ¯ A rehydrated version automatically moves to the Archive access tier after 30 days. No, the provided lifecycle management policy does not specify that a rehydrated version automatically moves to the Archive access tier after 30 days.
upvoted 1 times
...
JRH00
1 year ago
NNY is correct
upvoted 1 times
...
23169fd
1 year ago
Since snapshots are versions of blobs and the policy includes versioning, this statement is true.
upvoted 2 times
...
rdeleonp95
1 year, 1 month ago
NNN "A lifecycle management policy will not delete the current version of a blob until any previous versions or snapshots associated with that blob have been deleted. If blobs in your storage account have previous versions or snapshots, then you must include previous versions and snapshots when you specify a delete action as part of the policy" I guess that this is what Microsoft want to test you if there is not part or section marked as snapshot will be not applied the policy https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview#:~:text=3%20A%20lifecycle,of%20the%20policy.
upvoted 1 times
...
mkhlszf
1 year, 2 months ago
Answer should be NNN 1st N - The rule applies to "container1/". The field has 2 rules: a.This field is case sensitive b.There are no wilcards, those are assumed to already exist so "container1/" = "ANYTHINGHEREcontainer1" and "/container1" = "container1ANYTHINGHERE" A snapshot from a container has the same name of the container with an append at the end e.g "container1?snapshot=2011-03-09T01:42:34.9360000Z" so container1/ does not include the snapshot. 2nd N- The scope of the rule only includes container1 3rd N- You dont know when or how the rehydration happened, so you cant be 100% certain it will be archived after 30 days; if it was copied sure, if it happened to be changed to it 5 dasy ago, no. If your job depended on it, would you say yes?
upvoted 2 times
...
lexxone
1 year, 3 months ago
YES NO NO
upvoted 2 times
...
tashakori
1 year, 3 months ago
Correct
upvoted 2 times
...
ceazyongo
1 year, 4 months ago
NNN This rule is for version files only, there is no rule definition for baseBlob or snapshot files, see below code. Also MS says "Changing a blob's tier doesn't affect its last modified time.", so we can have a version file for 31 days old, and rehydrated 6 days ago, this file will not be archived. https://learn.microsoft.com/en-us/azure/storage/blobs/archive-rehydrate-overview rules: [ { definition: { actions: { baseBlob: { ... } snapshot: { ... } version: { ... } }
upvoted 2 times
...
93d821b
1 year, 6 months ago
I think its NNN. 1. The Lifecycle management only applies to container 1. It says nothing about container. Thus, when this says "A blob snapshot" its talking about 1 and 2. So no, because container 2 doesn't have a lifecycle policy. 2. No, because container 2 doesn't have a lifecycle policy. 3. No, same as #1. I checked and there is no automatic blob movement w/o a lifecycle management policy.
upvoted 7 times
Sanaz90
10 months, 1 week ago
Shouldn't the second one be yes? Because Blob index match is not supported as a filter for versions and snapshots?
upvoted 1 times
Sanaz90
10 months, 1 week ago
I need to correct myself because question is not using blob index match as filtering
upvoted 1 times
...
...
...
Ahkhan
1 year, 7 months ago
Yes, no no. DaysAfterLastTierGreaterThan is equivalent to skip archiving for x number of days after a blob has been rehyderated.
upvoted 2 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel