Profiles are split across two shares in one classic account. Each share is below its own limit, yet their combined workload reaches an account limit. What does the second share change?

Choose the single best answer.

A.It creates a wholly independent account-level IOPS budget
B.It guarantees no more sign-in latency without measurement
C.It partitions the data, but the account aggregate limit still applies
D.It removes the host NIC's limit automatically

Show the answer and explanation

✓ Correct answer

It partitions the data, but the account aggregate limit still applies

Share partitioning can help some limits, but it does not remove a shared account bottleneck. Evaluate the aggregate budget before expecting improvement. Option explanations: A. It creates a wholly independent account-level IOPS budget: A second share is not a second storage account. B. It guarantees no more sign-in latency without measurement: Account, host and network constraints still need assessment. C. It partitions the data, but the account aggregate limit still applies: Classic shares in one account share the account's aggregate resources and limits. D. It removes the host NIC's limit automatically: Data partitioning does not change the host NIC's throughput. Sources: Azure Files guidance for virtual desktop workloads — https://learn.microsoft.com/en-us/azure/storage/files/virtual-desktop-workloads; Understand Azure Files billing — https://learn.microsoft.com/en-us/azure/storage/files/understanding-billing

Read the source reference

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid, not affiliated with or endorsed by Microsoft. Original educational practice questions, not official exam questions or a prediction of an exam result. Use Microsoft Learn and hands-on labs alongside this course.