You are planning a Fabric analytics solution. You need to recommend a licensing strategy to support 10 Microsoft Power BI report authors and 600 report consumers. The solution must use Dataflow Gen2 for data ingestion and minimize costs. Which Fabric license type should you recommend?

You are planning a Fabric analytics solution. You need to recommend a licensing strategy to support 10 Microsoft Power BI report authors and 600 report consumers. The solution must use Dataflow Gen2 for data ingestion and minimize costs. Which Fabric license type should you recommend?

• A. F32
• B. F64
• C. F24
• D. F128

Answer: (B)

Licensing in Fabric is capacity-based: a chosen capacity tier provides the compute and memory shared by all authors and consumers in that workspace. For Dataflow Gen2 ingestion and for serving a large number of report consumers, you need enough headroom in the capacity to handle both ingestion workloads and concurrent report rendering. With 10 authors creating and refreshing dataflows and 600 readers viewing reports, a mid-range capacity offers a practical balance between performance and cost. It provides more ingestion throughput and better support for multiple concurrent report views than the smaller tiers, while not carrying the premium price of the largest tier. The smaller options risk bottlenecks in dataflow refresh and report rendering under load, and the largest option would be more than you need for this scale. So, the recommended choice is the mid-tier capacity, which delivers the necessary compute and memory to support Dataflow Gen2 ingestion and the 600 users while keeping costs reasonable.

Licensing in Fabric is capacity-based: a chosen capacity tier provides the compute and memory shared by all authors and consumers in that workspace. For Dataflow Gen2 ingestion and for serving a large number of report consumers, you need enough headroom in the capacity to handle both ingestion workloads and concurrent report rendering.

With 10 authors creating and refreshing dataflows and 600 readers viewing reports, a mid-range capacity offers a practical balance between performance and cost. It provides more ingestion throughput and better support for multiple concurrent report views than the smaller tiers, while not carrying the premium price of the largest tier. The smaller options risk bottlenecks in dataflow refresh and report rendering under load, and the largest option would be more than you need for this scale.

So, the recommended choice is the mid-tier capacity, which delivers the necessary compute and memory to support Dataflow Gen2 ingestion and the 600 users while keeping costs reasonable.