In which scenario might you be most likely to use a list attribute?

In which scenario might you be most likely to use a list attribute?

• A. Buffering point features.
• B. Calculating a new value by adding two attributes together.
• C. Storing the name and address of multiple community centers that intersect neighborhood polygons.
• D. Using a regular expression to replace values in a string attribute.

Answer: (C)

A list attribute is used when one feature is related to multiple values. In this scenario, a neighborhood polygon intersects several community centers, so you want to keep all those centers’ names and addresses together in one attribute as a list. This preserves the full set of related items for that polygon rather than dropping extras to fit into a single value. The other tasks involve single-value operations: buffering is a spatial operation applied to each point, arithmetic on two attributes is a calculation between scalar values, and a regex replaces within a single string. Using a list attribute lets you store multiple related strings (or IDs) for the intersecting centers in one field, which is exactly what’s needed when handling multi-valued relationships.

A list attribute is used when one feature is related to multiple values. In this scenario, a neighborhood polygon intersects several community centers, so you want to keep all those centers’ names and addresses together in one attribute as a list. This preserves the full set of related items for that polygon rather than dropping extras to fit into a single value. The other tasks involve single-value operations: buffering is a spatial operation applied to each point, arithmetic on two attributes is a calculation between scalar values, and a regex replaces within a single string. Using a list attribute lets you store multiple related strings (or IDs) for the intersecting centers in one field, which is exactly what’s needed when handling multi-valued relationships.