An analyst sets valid values for an attribute. Which domain type should be used to constrain the values to a specific set?

The chosen response of coded value is the appropriate domain type to constrain attribute values to a specific set. Coded value domains allow you to define a list of allowable entries for an attribute, which can be especially useful for categories that have a finite number of options. For example, if you were creating a database for different types of land use, you could establish a coded value domain that lists "Residential," "Commercial," "Industrial," etc. This ensures consistency and accuracy in the data entry process, as users can only select from the predefined options, reducing the chance of typographical errors or the entry of invalid data.

In contrast, range domains set boundaries for numerical values, such as specifying that an attribute can only be between 1 and 100. This is effective for numerical data but does not apply when you need to limit entries to a specific set of non-numeric categories. The other options, including Z and M, are generally related to geometrical properties in spatial data and do not pertain directly to attribute values in the way that coded value domains do. Therefore, for creating a controlled vocabulary or allowed choices for an attribute, coded value domains are the correct choice.