Exam AZ-204 All Questions

View all questions & answers for the AZ-204 exam

Exam AZ-204 topic 3 question 9 discussion

Actual exam question from Microsoft's AZ-204

Question #: 9
Topic #: 3

DRAG DROP -
You are maintaining an existing application that uses an Azure Blob GPv1 Premium storage account. Data older than three months is rarely used.
Data newer than three months must be available immediately. Data older than a year must be saved but does not need to be available immediately.
You need to configure the account to support a lifecycle management rule that moves blob data to archive storage for data not modified in the last year.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:

Show Suggested Answer

Suggested Answer:

by Marusyk at March 14, 2021, 1:21 a.m.

Comments

Submit Cancel

sien

Highly Voted 4 years, 2 months ago

Since we already have a premium P1 account with gpv1. Why not: - Upgrade the existing one to GPv2 - Create a new GPV2 standard account with default access level to cool - And then copy archive data to the GPV2 and delete the data from original storage account. That makes sense to me.

upvoted 124 times

jay158

4 years ago

Is there any requirement in question, which says set default access tier to COOL? Please clarify.

upvoted 2 times

lighting

3 years, 11 months ago

I have 2 ideas: 1. - One HOT for newer than 3 months - One COOL for older than 3 months and Archive data. 2. - One HOT for non-archived data. Can be accessed immediately. Because they just said "Older than 3 months data are rarely accessed" but didn't tell us anything about can it be accessed immediately. - One COOL for archived data. Archived tier can just be set at blob level. "Only the hot and cool access tiers can be set at the account level. The archive access tier can only be set at the blob level" https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers

upvoted 4 times

...

WillPassExam

4 years, 2 months ago

does this mean at the end, we have 2 GPv2 storage accounts, one access level is cool (for archive data) and the other is hot?

upvoted 2 times

sien

4 years, 2 months ago

I would say so.

upvoted 1 times

...

sien

4 years, 2 months ago

Also look at this blog: https://www.apptio.com/blog/essential-guide-azure-blob-storage-pricing/ Only GPv2 and Blob storage accounts support tiering. If you are using GPv1, and you want to leverage tiering, convert your account to GPv2 through the Azure portal.

upvoted 4 times

...

ferut

4 years, 1 month ago

My choice as well

upvoted 1 times

...

Chked

3 years, 10 months ago

I agree. But can the first step be the last? - Create a new GPV2 standard account with default access level to cool - And then copy archive data to the GPV2 and delete the data from original storage account. - Upgrade the existing one to GPv2

upvoted 1 times

...

Load full discussion...

...

mlantonis

Highly Voted 4 years ago

Step 1: Upgrade the storage account to GPv2 Object storage data tiering between hot, cool, and archive is supported in Blob Storage and General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts don't support tiering. You can easily convert your existing GPv1 or Blob Storage accounts to GPv2 accounts through the Azure portal. Step 2: Create a new GPV2 standard account with default access level to cool Step 3: Copy the data to be archived to a Standard GPv2 storage account and then delete the data from the original storage account

upvoted 23 times

tosm

3 years ago

Agreed: 1. upgrade storage account 1 from GPv1 -> v2 (hot), 2. create storage account 2 GPv2 (cool) 3. copy data from account 1 to account 2. End result: account 1 (hot), account 2(cool and archive) both accounts can set lifecycle policy

upvoted 4 times

...

mlantonis

4 years ago

Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers https://docs.microsoft.com/en-us/azure/storage/common/storage-account-upgrade?tabs=azure-portal

upvoted 2 times

...

mlantonis

4 years ago

Although Step 3 seems unusual and not necessary.

upvoted 4 times

ensa

3 years, 8 months ago

every time with good explanation but step 3 needed because why not transfer the old data that needed to new one and delete the old one for saving cost

upvoted 1 times

...

8ac3742

Most Recent 10 months, 2 weeks ago

In real practice, I just keep one account: upgrade the account to GPV2 which supports tier, change the account tier to cool since the data in the account is infrequently used, and achieve the blob which is not modified for more than 1 year.

upvoted 1 times

...

Christian_garcia_martin

10 months, 2 weeks ago

Upgrade , Create and Copy

upvoted 1 times

...

11_NickName_11

1 year, 6 months ago

Why to upgrade the storage account to GPv2?

upvoted 2 times

...

AlbertoBT

1 year, 7 months ago

The requirement is just: You need to configure the account to SUPPORT a lifecycle management rule. So you only need "Upgrade the existing one to GPv2" No more steps from the list are required Then you could configure the lifecycle management rule. Once you apply the rule, the files tier will be changed automatically

upvoted 2 times

...

narenazure

2 years, 2 months ago

Azure Blob storage lifecycle management offers a rich, rule-based policy for General Purpose v2 and Blob storage accounts.

upvoted 1 times

...

deepak_26

2 years, 2 months ago

Create , change , copy Data stored in a premium block blob storage account cannot be tiered to Hot, Cool, or Archive using Set Blob Tier or using Azure Blob Storage lifecycle management. To move data, you must synchronously copy blobs from the block blob storage account to the Hot tier in a different account using the Put Block From URL API or a version of AzCopy that supports this API.

upvoted 3 times

...

motekim

2 years, 2 months ago

Just for reference: GPv2 supports Hot, Cool, and Archive tiers

upvoted 2 times

...

dimsok

2 years, 4 months ago

Upgrade-Create-Copy

upvoted 2 times

...

JamieS

2 years, 4 months ago

Seems like we don't have the entire world view, and that there's already an existing standard v2 account elsewhere. If that's the case we're starting with v1 storage where the data currently is and we also have a default v2 storage that exists. We upgrade the current v1 to v2 so we can access lifetime management we copy the data to be archived to the standard v2 (that already existed, and by default has hot tier) then we set the tier to be cool (where the archive data was just copied to). I think the current answer is correct.

upvoted 2 times

...

micro9000

2 years, 7 months ago

The answer doesn't make any sense to me. in the 2nd step, it says copy the data from old storage account to new one, it means there are 2 storage accounts, why you need to upgrade the existing?

upvoted 2 times

...

Akiu

2 years, 7 months ago

Upgrade to GPv2 Copy data Change tier to cool You can't create the second account in a cool tier because of this: Data stored in a premium block blob storage account cannot be tiered to hot, cool, or archive using Set Blob Tier or using Azure Blob Storage lifecycle management. To move data, you must synchronously copy blobs from the block blob storage account to the hot tier in a different account using ... https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview#blob-lifecycle-management

upvoted 1 times

...

Azziet

2 years, 11 months ago

Upgrade Create Copy

upvoted 7 times

...

Evo_Morales

3 years, 2 months ago

Agree with voting/answer, but the question itself seems flawed. Need to learn not to read anything else into the questions and not add steps/requirements that yes, would make sense.

upvoted 3 times

...

petitbilly

3 years, 3 months ago

Got it in exam 03/22

upvoted 5 times

...

massnonn

3 years, 4 months ago

for me not have sense - Upgrade the existing one to GPv2 So: -create .. -change.. -copy

upvoted 1 times

...

Load full discussion...