An Azure service that stores unstructured data in the cloud as blobs.
Changing the Azure portal display language to English and entering Yes is a valid workaround for this exam-lab issue, but the available Microsoft documentation does not establish a general defect in the Spanish portal.
What is documented
For a container-scoped, time-based retention policy, the supported portal workflow is:
- Open the container.
- Select Access policy.
- Under Immutable blob versions, locate the unlocked policy.
- Select More → Lock policy.
- Confirm the operation.
- Verify that the policy is shown as locked. ^1^
The documentation only says to confirm the operation; it does not document whether the confirmation field must accept Sí, Yes, or another localized value. Therefore, the result establishes an effective workaround, but not whether the underlying problem was:
- Spanish confirmation validation,
- stale or partially localized portal code, or
- a constraint in the certification lab environment.
Important consequence of locking
Locking is effectively irreversible: after the policy is locked, it cannot be deleted and its retention period cannot be shortened. The retention interval can only be extended, and protected blobs cannot be deleted until their retention expires. Review the policy duration carefully before selecting Lock policy. ^1^
If this happens in another exam
Use the same non-destructive workaround:
- Azure portal → Settings → Language + region.
- Change the display language to English and apply it.
- Return to the container’s Access policy.
- Select Lock policy, enter Yes, and submit.
- Confirm that the status changes to Locked.
Also record the approximate time, selected portal language, exact text entered, and screenshots if exam rules permit. Microsoft directs candidates who encounter lab problems to submit them through the Exam item challenge process so the issue can be investigated. ^2^
Outside an exam environment
If the portal confirmation still fails in a normal Azure subscription, the policy can be locked with Azure CLI by retrieving its current ETag and passing it to the lock operation:
etag=$(az storage container immutability-policy show \
--account-name <storage-account> \
--container-name <container> \
--query etag --output tsv)
az storage container immutability-policy lock \
--resource-group <resource-group> \
--account-name <storage-account> \
--container-name <container> \
--if-match "$etag"
Use this only after confirming the retention settings because the same irreversible locking behavior applies. ^1^
References