Why would you use address_type versus address_role in address modeling?

Why would you use address_type versus address_role in address modeling?

• A. Address_type and address_role mean the same thing and can be used interchangeably.
• B. Address_type categorizes the nature of the address, while address_role defines its usage (shipping or billing); both support flexible business rules.
• C. Address_role determines the geographic region of the address.
• D. There is no difference; one is deprecated.

Answer: (B)

In address modeling, separate concepts for what an address is and how it’s used give you real flexibility. Address_type captures the nature of the address itself—examples include residential, business, PO Box, or rural route. This tells you about the address’s characteristics and what rules or formatting apply to it, independent of why you’re collecting it.

Address_role, on the other hand, defines how that address will be used in business processes—such as shipping, billing, or mailing. This governs which workflows can reference the address and what validations or permissions apply when you assign it to an order, a customer profile, or an invoice.

Keeping these concerns distinct lets you mix and match: you can have multiple addresses for a single entity with different roles, and you can have various types of addresses that serve specific roles. It supports clear validation (e.g., only addresses with a shipping role can be used for delivery) and makes it easy to adapt rules as business needs evolve.

The idea that both concepts mean the same thing is inaccurate, and geographic region isn’t determined by address_role. Also, both concepts aren’t interchangeable or deprecated; they serve different purposes and work together to enable flexible, rule-driven address management.