Which scenario is a typical use of a list attribute?

• A. Storing a single ID per feature.
• B. Storing multiple Store IDs per feature.
• C. Storing a single digit.
• D. Storing only date strings.

Answer: (B)

A list attribute is meant to hold a collection of values under one attribute for a single feature, which is ideal when a feature is related to several items. Storing multiple Store IDs per feature captures a one-to-many relationship in one place, so you can represent all related stores without creating additional fields or features. The other options describe single-valued data—just one ID, a single digit, or a single date string—so they don’t require or leverage a list. If you needed multiple dates or multiple IDs, a list would be appropriate, but the scenario given clearly aligns with storing multiple IDs.