What action must occur when creating a virtual volume in a consistency group?

When creating a virtual volume in a consistency group, it is essential that the virtual volume is mapped to a storage volume in a 1:1 relationship. This 1:1 mapping is crucial because consistency groups are designed to ensure that multiple virtual volumes maintain data consistency across different points in time. By having a straightforward one-to-one mapping, the system can effectively manage the data and ensure that all volumes within the consistency group are treated as a single entity when it comes to snapshots or replication events.

This mapping allows the underlying technology to enforce policies and maintain recovery point objectives since each virtual volume in the consistency group corresponds directly to its storage volume. It ensures that operations on the consistency group, such as taking snapshots or performing failovers, are synchronized across all volumes, thereby preserving the integrity and reliability of the data.

In contrast, other conditions presented in the choices do not align with the requirements for creating a virtual volume within a consistency group. For instance, initiating from a local device or utilizing external storage may represent different considerations in the architecture but do not impact the necessity for a 1:1 mapping. Similarly, detaching from any other group could affect the flexibility of volume management but is not a requisite for creating a new virtual volume in a consistency group