Question 1mediummultiple choice
Full question →mediummultiple choiceObjective-mapped
You have a storage account named stproddata01 that contains application data in a blob container. Users sometimes delete blobs accidentally and need a way to recover those deleted blobs for several days. You want the simplest solution with minimal operational effort. What should you configure?
Answer choices
Why each option matters
Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.
A
Distractor review
Configure blob versioning only.
Versioning helps preserve previous versions but is not the most direct answer to recovering deleted blobs.
B
Best answer
Configure blob soft delete.
Blob soft delete retains deleted blobs for a retention period and supports recovery with minimal effort.
C
Distractor review
Configure lifecycle management rules.
Lifecycle management automates transitions and deletions but does not provide deleted blob recovery by itself.
D
Distractor review
Move the container to the Archive access tier.
Archive is for low-cost storage of infrequently accessed data, not deletion recovery.
Common exam trap
Common exam trap: answer the scenario, not the keyword
A frequent exam trap is selecting blob versioning as the solution for recovering deleted blobs. While versioning preserves previous versions of a blob, it does not retain blobs once they are deleted. Candidates might confuse versioning’s ability to track changes with the ability to recover deleted data, but only blob soft delete retains deleted blobs for recovery. Misunderstanding this distinction leads to incorrect answers, as versioning alone cannot restore blobs that users have deleted accidentally.
Technical deep dive
How to think about this question
Blob soft delete is a feature in Azure Storage that protects blobs from accidental deletion by retaining deleted blobs for a specified retention period. When enabled, any blob deleted within this period is not permanently removed but marked as soft deleted, allowing recovery. This feature is essential for scenarios where users might accidentally delete important data, as it provides a safety net without requiring complex backup solutions. The decision to use blob soft delete over other options like blob versioning or lifecycle management hinges on the specific recovery needs. Blob versioning tracks changes and preserves previous versions of blobs but does not inherently protect against deletion. Lifecycle management automates data movement and expiration but does not retain deleted blobs for recovery. The Archive tier is optimized for cost savings on rarely accessed data and does not facilitate recovery from deletion. Therefore, blob soft delete is the most straightforward and operationally minimal solution for recovering deleted blobs. A common exam trap is confusing blob versioning with blob soft delete, assuming versioning alone can recover deleted blobs. While versioning helps with overwrites, it does not retain blobs after deletion. Practically, enabling blob soft delete ensures that deleted blobs remain recoverable for the retention period, simplifying data protection strategies in Azure Storage environments. This feature is critical for maintaining data integrity and availability in production storage accounts like stproddata01.
KKey Concepts to Remember
- Blob soft delete in Azure Storage retains deleted blobs for a configurable retention period, allowing recovery without complex operational steps.
- Blob versioning preserves previous versions of blobs but does not directly enable recovery of deleted blobs, making it less suitable for accidental deletions.
- Lifecycle management rules automate blob tiering and deletion based on policies but do not provide a direct mechanism to recover deleted blobs.
- The Archive access tier is designed for long-term, low-cost storage of infrequently accessed data and does not support blob recovery after deletion.
- Configuring blob soft delete requires enabling the feature and setting a retention period, which defines how long deleted blobs remain recoverable.
- Blob soft delete simplifies recovery by automatically retaining deleted data, reducing the need for manual backup or complex restore operations.
- Users can restore blobs deleted within the retention period by undeleting them, which is supported natively by Azure Storage with soft delete enabled.
- Choosing blob soft delete aligns with minimal operational effort and simplicity, critical for environments where accidental deletion is common.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Related practice questions
Related 200-301 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
CCNA subnetting practice questions
Practise IPv4 subnetting, CIDR, masks, host ranges and subnet selection.
CCNA OSPF practice questions
Practise OSPF neighbours, router IDs, metrics, areas and routing-table interpretation.
CCNA VLAN practice questions
Practise VLANs, access ports, trunks, allowed VLANs and switching scenarios.
CCNA STP practice questions
Practise spanning tree, root bridge election, port roles and STP troubleshooting.
CCNA EtherChannel practice questions
Practise LACP, PAgP, port-channel behaviour and bundle requirements.
CCNA ACL practice questions
Practise standard and extended ACLs, permit/deny logic and traffic filtering.
CCNA NAT practice questions
Practise static NAT, dynamic NAT, PAT and inside/outside address translation.
CCNA DHCP practice questions
Practise DHCP scopes, relay, leases and troubleshooting.
CCNA show ip route practice questions
Practise routing-table output, longest-prefix match, AD and route selection.
CCNA show interfaces trunk practice questions
Practise trunk verification and VLAN forwarding across switches.
CCNA wireless security practice questions
Practise WLAN security, authentication and wireless architecture concepts.
CCNA IPv6 practice questions
Practise IPv6 addressing, routes, neighbour discovery and common IPv6 exam traps.
More questions from this exam
Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.
Question 1
A router learns the same prefix from both OSPF and EIGRP. Which route is installed by default?
Question 2
A router shows this output: R1#show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.1.1.2 1 FULL/DR 00:00:34 192.168.12.2 GigabitEthernet0/0 10.1.1.3 1 2WAY/DROTHER 00:00:39 192.168.12.3 GigabitEthernet0/0 Which statement is correct?
Question 3
What is the OSPF metric called?
Question 4
A non-root switch has two uplinks toward the root bridge. One path has a lower total STP cost than the other. What role will the lower-cost uplink have?
Question 5
A router interface applies this ACL inbound: 10 deny tcp any any eq 80 20 permit ip any any A user reports that web browsing to a server by IP address fails, but ping works. Which statement best explains the behavior?
Question 6
A router learns route 198.51.100.0/24 from OSPF with AD 110 and also has a static route to the same prefix configured with AD 150. Which route is installed?
FAQ
Questions learners often ask
What does this 200-301 question test?
Blob soft delete in Azure Storage retains deleted blobs for a configurable retention period, allowing recovery without complex operational steps.
What is the correct answer to this question?
The correct answer is: Configure blob soft delete. — Blob soft delete is designed to retain deleted blobs for a defined retention period so they can be restored. Lifecycle management controls movement and deletion based on rules, Archive tier is for low-cost storage, and blob versioning is useful for overwrite history but is not the most direct control for recovering deleted blobs.
What should I do if I get this 200-301 question wrong?
Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.
Discussion
Loading comments…
Sign in to join the discussion.