When architecting a table in Amazon DynamoDB to catalog customer interactions that occur at various points in time, with the necessity to retrieve entries based on individual customer and specific date ranges, what key schema should the developer implement to support this access pattern efficiently?
Implement a single unique identifier for all interactions without additional keys.
Rely solely on the customer reference for the table's partition key without incorporating a sort element.
Design the table with a partition element for individual customer reference and a sort element capturing the time aspect of interactions.
Utilize only the time parameter of the interactions as the table's partition key without considering customer-specific sorting.