What is the purpose of the AddressHistory entity in the data model?

What is the purpose of the AddressHistory entity in the data model?

• A. Tracks address changes over time
• B. Stores user passwords
• C. Logs API requests
• D. Holds country codes

Answer: (A)

The idea being tested is how to record changes to where someone lives over time. AddressHistory is used to store each past address along with when it became effective (and sometimes when it ended). This lets you answer questions like “where did this user live on a specific date?” or “how many times did their address change?” without losing previous data, supporting audits, billing, compliance, and historical reporting. This isn’t about passwords, API logs, or country codes. Passwords belong in secure authentication data, API logs belong in system usage logs, and country codes are typically part of the address fields or a reference table, not a historical record of changes. AddressHistory focuses on preserving the sequence of address changes and the time periods they were active.

The idea being tested is how to record changes to where someone lives over time. AddressHistory is used to store each past address along with when it became effective (and sometimes when it ended). This lets you answer questions like “where did this user live on a specific date?” or “how many times did their address change?” without losing previous data, supporting audits, billing, compliance, and historical reporting.

This isn’t about passwords, API logs, or country codes. Passwords belong in secure authentication data, API logs belong in system usage logs, and country codes are typically part of the address fields or a reference table, not a historical record of changes. AddressHistory focuses on preserving the sequence of address changes and the time periods they were active.