You want to use Azure NetApp Files to create a volume in an existing capacity pool-In this scenario, which statement about volumes is true?

The storage hierarchy in Azure NetApp Files is foundational to its architecture. A capacity pool is a provisioned amount of storage capacity at a specific service level (Standard, Premium, or Ultra). This pool acts as a container from which you can create one or more volumes. Each volume resides entirely within a single capacity pool and inherits its service level. This one-to-many relationship (one capacity pool to multiple volumes) is a core concept, allowing for flexible management and allocation of storage resources to different workloads.

A. This is an incomplete statement. While a move is restricted to the same region, the more direct and specific constraint is that the destination capacity pool must be in the same NetApp account.

B. This statement describes a specific management operation (moving a volume), which is true, but option C describes a more fundamental and defining architectural characteristic of Azure NetApp Files.

D. A volume is a child resource of a single capacity pool. It cannot exist in or draw capacity from multiple capacity pools simultaneously, as this would violate the storage hierarchy model.

1. Microsoft Azure Documentation, "Storage hierarchy of Azure NetApp Files": This document explicitly outlines the relationship between NetApp accounts, capacity pools, and volumes. The diagram and text confirm that a capacity pool is a container for volumes. It states, "You create volumes within a capacity pool," implying a one-to-many relationship. This directly supports answer C and refutes D.

Reference: Microsoft Docs, Azure NetApp Files documentation, "Storage hierarchy of Azure NetApp Files".

2. Microsoft Azure Documentation, "Create a capacity pool for Azure NetApp Files": This guide details the process of setting up a capacity pool and explicitly mentions its purpose. The document states, "After you create a capacity pool, you can create volumes within the capacity pool." This reinforces that a pool is designed to hold multiple volumes.

Reference: Microsoft Docs, Azure NetApp Files documentation, "Quickstart: Set up Azure NetApp Files and create an NFS volume", Step 2: Create a capacity pool.

3. Microsoft Azure Documentation, "Dynamically change the service level of a volume for Azure NetApp Files": This document explains the process of moving a volume between capacity pools. It specifies the constraints: "The new capacity pool must be in the same NetApp account." Since a NetApp account is region-specific, this confirms that options A and B describe a valid but specific operation, making them less fundamental than the structural truth in option C.

Reference: Microsoft Docs, Azure NetApp Files documentation, "Dynamically change the service level of a volume for Azure NetApp Files", section "Requirements and considerations".