mediummultiple choiceObjective-mapped

An application team plans to store block blobs for application logs, lifecycle them to cooler tiers over time, and use Azure Monitor diagnostic exports from several Azure resources into the same storage account. They also want access tier controls and general-purpose features in one place. Which storage account type should the administrator create?

Question 1mediummultiple choice
Full question →

An application team plans to store block blobs for application logs, lifecycle them to cooler tiers over time, and use Azure Monitor diagnostic exports from several Azure resources into the same storage account. They also want access tier controls and general-purpose features in one place. Which storage account type should the administrator create?

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

BlobStorage account, because it is optimized for storing only unstructured blobs.

A BlobStorage account can store blobs, but it is narrower in scope than a general-purpose v2 account and is not the best answer when broad Azure integration and tiering features are required.

B

Best answer

StorageV2 general-purpose account, because it supports blobs, tiering, and broad Azure integrations.

A StorageV2 account is the standard choice when you need blob capabilities, access tiers, lifecycle policies, and broad service integration. It supports common operational tasks without limiting the team to a specialized storage type.

C

Distractor review

FileStorage account, because it supports any Azure diagnostic data format and access tiers.

FileStorage is intended for premium Azure Files workloads. It is not the correct account type for blob-centric logging and lifecycle management requirements.

D

Distractor review

BlockBlobStorage account, because it is required whenever logs are exported from Azure Monitor.

BlockBlobStorage is designed for high-performance block blob workloads, usually with premium characteristics. It is not required just because logs are being exported, and it is less broadly flexible than StorageV2.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related AZ-104 practice-question pages

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

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.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: StorageV2 general-purpose account, because it supports blobs, tiering, and broad Azure integrations. — A general-purpose v2 storage account is the most appropriate choice because it supports the blob features the team needs, including access tiers and lifecycle management, while also remaining flexible for operational integrations such as diagnostic exports. It is the standard, widely compatible storage account type for most Azure workloads. The scenario does not require the narrower specialization of BlobStorage or the premium constraints of FileStorage or BlockBlobStorage. Why others are wrong: BlobStorage is functional for blobs, but StorageV2 is the preferred modern option because it offers broader capabilities and better operational flexibility. FileStorage is for Azure Files, not blob logging workloads. BlockBlobStorage is specialized for premium block blob performance and is unnecessary when the team simply needs tiering and general-purpose service compatibility.

What should I do if I get this AZ-104 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.