Ursa Major Solar wants to ensure that unique data is always input into a specific field. Which two field properties should the administrator configure?

To ensure that unique data is always input into a specific field, one of the critical field properties to configure is the uniqueness constraint. This attribute prevents duplicate entries in that particular field, thereby ensuring the integrity of the data. While making a field required ensures that users must enter a value, it does not inherently enforce uniqueness — users could still enter the same value multiple times.

Setting a field as required guarantees that an entry must be made, but unless coupled with a unique constraint, it does not restrict the data input from being repetitive. Thus, by configuring the uniqueness property, the administrator can ensure that no two entries in that specific field can be the same, which is essential for maintaining distinct data values.

On the other hand, a default value can help auto-populate fields but does not address uniqueness. The data type defines what kind of data can be entered but does not enforce uniqueness either. So, while having fields set to required is essential for data entry, ensuring that the data remains unique is a separate but equally important configuration. Therefore, determining the uniqueness of the field directly achieves the requirement of unique data entries.