Which statement describes a common use case for List attributes?

Which statement describes a common use case for List attributes?

• A. Storing independent attributes
• B. Storing multiple values in a single attribute
• C. Storing spatial coordinates
• D. Storing dataset metadata

Answer: (B)

List attributes hold multiple values in a single field, making them the natural choice when a feature needs to carry several related values without creating a separate attribute for each one. This is useful for representing multi-valued properties like multiple codes, tags, or owners within one attribute. For example, a parcel feature could have a list attribute called Owners containing multiple names, or a feature might store several permit numbers in one attribute. Storing independent attributes would require multiple separate fields, not a single multi-valued field. Spatial coordinates belong to the geometry rather than a list attribute, and dataset metadata is information about the dataset as a whole, not a per-feature multi-valued attribute.

List attributes hold multiple values in a single field, making them the natural choice when a feature needs to carry several related values without creating a separate attribute for each one. This is useful for representing multi-valued properties like multiple codes, tags, or owners within one attribute.

For example, a parcel feature could have a list attribute called Owners containing multiple names, or a feature might store several permit numbers in one attribute.

Storing independent attributes would require multiple separate fields, not a single multi-valued field. Spatial coordinates belong to the geometry rather than a list attribute, and dataset metadata is information about the dataset as a whole, not a per-feature multi-valued attribute.