Examkin

Question

Difficulty: HardImplement Azure Blob Storage Lifecycle Management and Retention Policies

A healthcare provider uses a Standard General Purpose v2 (GPv2) storage account to store patient medical records in a container named `patient-records`.

You need to define an Azure Blob Storage lifecycle management policy that meets the following requirements:
* Automatically transitions block blobs from the Hot tier to the Cool tier 180 days after they were last modified.
* Automatically transitions block blobs to the Archive tier 365 days after they were last modified.
* Automatically deletes block blobs 3650 days after they were last modified.
* Restricts the policy rules to apply only to blobs in the `patient-records` container that have a blob index tag named `ArchiveStatus` set to a value of `Ready`.

Which two of the following configuration fragments or statements are correct for this policy implementation? Select two.

  1. "actions": {
    "baseBlob": {
    "tierToCool": {
    "daysAfterModificationGreaterThan": 180
    },
    "tierToArchive": {
    "daysAfterModificationGreaterThan": 365
    },
    "delete": {
    "daysAfterModificationGreaterThan": 3650
    }
    }
    }    Answer
  2. "filters": {
    "blobTypes": [ "blockBlob" ],
    "prefixMatch": [ "patient-records/" ],
    "blobIndexMatch": [
    {
    "name": "ArchiveStatus",
    "op": "==",
    "value": "Ready"
    }
    ]
    }    Answer
  3. C
    "filters": {
    "blobTypes": [ "blockBlob" ],
    "prefixMatch": [ "patient-records/" ],
    "blobIndexMatch": [
    {
    "name": "archivestatus",
    "op": "==",
    "value": "ready"
    }
    ]
    }
  4. D
    The lifecycle management policy requires you to generate a Shared Access Signature (SAS) token with container-level write, delete, and list permissions, and assign this token in the policy's properties to authorize execution.

Answer

The correct configuration fragments are the actions block specifying the tiering and deletion thresholds using 'daysAfterModificationGreaterThan', and the filters block matching the case-sensitive 'ArchiveStatus' tag with value 'Ready' for block blobs in the 'patient-records/' container prefix.
The correct configuration fragments define the appropriate actions and filters using the official Azure Blob Storage lifecycle management schema. The actions block correctly uses 'daysAfterModificationGreaterThan' to specify the duration in days for transitioning blobs to Cool, Archive, and deleting them. The filters block correctly applies a case-sensitive 'blobIndexMatch' matching the tag name 'ArchiveStatus' and the value 'Ready' on block blobs in the 'patient-records' container.

Step-by-Step Solution

1
Select the correct transition and deletion actions using the standard lifecycle management schema.
Identify that the actions block must configure 'tierToCool', 'tierToArchive', and 'delete' under 'baseBlob', specifying 'daysAfterModificationGreaterThan' with values 180, 365, and 3650 respectively.
Lifecycle rules require 'daysAfterModificationGreaterThan' to evaluate when to move or delete blobs based on their last modified time.
2
Select the correct filter block to limit policy execution to the specific container and tag.
Identify that the filter block must define 'prefixMatch' as 'patient-records/' and configure the 'blobIndexMatch' array with case-sensitive name 'ArchiveStatus' and value 'Ready'.
Lifecycle filters allow prefix matching and key-value blob index tag matching. These matches are case-sensitive.

Key Concept

Azure Blob Storage Lifecycle Management policy schema configuration, including action definitions, prefix filtering, and case-sensitive blob index tag matching.
Rate this question

Topics

Implement Azure Blob Storage Lifecycle Management and Retention Policies

More questions from this topic