Which data consistency settings can be achieved using UI Policy? (Choose three.)

UI policies can make fields visible or hidden based on conditions, which indirectly helps in ensuring data consistency by guiding users to enter data in specific fields that are pre-configured to accept data in an expected format (e.g., a date field appearing only when relevant).

UI policies can make fields editable only when relevant conditions are met, which helps ensure that data entered into those fields (whose length is defined at the dictionary level) adheres to character limits when made available for input.

While UI policies can hide fields, making a field hidden primarily controls visibility rather than directly setting rules for the format or content of data that is 'accepted' once the field is presented.

UI policies directly ensure data consistency by preventing unauthorized or premature modifications to fields by setting them as read-only based on specific conditions, thus preserving the integrity of existing data.

Making a field mandatory ensures data presence but does not directly control the specific format or character length of the data entered, which is a key aspect of consistency related to content and structure.