Question 691 of 1,000
Secure compute, storage, and databaseshardMultiple SelectObjective-mapped

Quick Answer

The answer is blob soft delete and versioning, as these two features work together to protect Azure Storage data from both accidental and malicious deletion. Blob soft delete retains deleted blobs for a configurable retention period, allowing recovery from inadvertent removal, while versioning preserves every overwrite as a separate version, enabling restoration to a prior state if a blob is maliciously overwritten or deleted. On the AZ-500 exam, this pairing tests your understanding of layered defense-in-depth for storage accounts, often appearing in scenario-based questions where you must choose the combination that prevents permanent data loss without relying on backups. A common trap is selecting only soft delete and forgetting versioning, which is critical for overwrite protection—soft delete alone cannot recover a blob that has been replaced. Remember the mnemonic “Save and Version” to recall that soft delete saves deleted blobs, and versioning saves overwritten states.

AZ-500 Secure compute, storage, and databases Practice Question

This AZ-500 practice question tests your understanding of secure compute, storage, and databases. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A storage account contains regulated records. Which two features help protect against accidental or malicious deletion?

Question 1hardmulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Blob soft delete and versioning

Blob soft delete protects against accidental deletion by retaining deleted blobs for a specified retention period, allowing recovery. Versioning preserves previous versions of blobs, enabling restoration to an earlier state if malicious overwrites or deletions occur. Together, they provide a layered defense against both accidental and intentional data loss.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Blob soft delete and versioning

    Why this is correct

    Correct for the stated requirement.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Disabling all encryption

    Why it's wrong here

    This does not meet the stated requirement as directly as the correct option.

  • Public container access

    Why it's wrong here

    This does not meet the stated requirement as directly as the correct option.

  • Immutable storage retention policies

    Why this is correct

    Correct for the stated requirement.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may confuse immutable storage retention policies (which prevent modification/deletion but are designed for compliance, not recovery from accidental deletion) with soft delete and versioning, which specifically address recovery after deletion.

Detailed technical explanation

How to think about this question

Blob soft delete works by moving deleted blobs to a 'soft-deleted' state where they are invisible to normal list operations but remain recoverable via the Undelete Blob REST API (Set Blob Properties with x-ms-delete-snapshots). Versioning creates a new version ID for each write operation, allowing point-in-time recovery using the x-ms-version-id header. In a real-world scenario, a malicious script that deletes blobs can be mitigated by soft delete's retention policy (default 7 days, configurable up to 365 days) and versioning's ability to restore overwritten data.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

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.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related AZ-500 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-500 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-500 question test?

Secure compute, storage, and databases — This question tests Secure compute, storage, and databases — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Blob soft delete and versioning — Blob soft delete protects against accidental deletion by retaining deleted blobs for a specified retention period, allowing recovery. Versioning preserves previous versions of blobs, enabling restoration to an earlier state if malicious overwrites or deletions occur. Together, they provide a layered defense against both accidental and intentional data loss.

What should I do if I get this AZ-500 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on AZ-500

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are responsible for securing Azure Storage accounts that contain confidential documents. You need to implement a solution that prevents accidental deletion of storage accounts and ensures that deleted blobs can be recovered within 30 days. Which two actions should you take?

medium
  • A.Configure an immutability policy
  • B.Enable blob soft delete with a retention period of 30 days
  • C.Enable container soft delete
  • D.Apply a CanNotDelete resource lock to the storage account
  • E.Configure network rules to block all public access

Why B: Option A is correct because a resource lock prevents deletion of the storage account. Option D is correct because soft delete for blobs allows recovery within the specified retention period. Option B (containers) is for versioning for blobs, not deletion prevention. Option C (immutability policy) is for legal hold, not recovery. Option E (firewall) is for access control.

Keep practising

More AZ-500 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.