A data model gives a business value a declared type and constraint. A cost is a quantity; a supplier code can contain leading zeroes that must survive intact. A choice limits allowed classifications, while requiredness describes whether a value must be present. Those rules should follow the business meaning.
The local source supports text, number and Boolean fields with required flags. Status is represented as text, so the course distinguishes that fixture from a real Dataverse choice record and its option metadata. You inspect these modeling decisions, then configure a local view and conditional form rule. The exercises do not claim to create a real table or deploy production metadata.