Your Azure Cosmos DB account uses the continuous backup (v2) policy. A bug corrupted a container 4 hours ago. You must recover the container’s state from 4 hours ago without overwriting the current data so you can compare and validate fixes. What should you do? (Select two)

Continuous backup (v2) in Azure Cosmos DB allows for point-in-time restore (PITR) of data. To recover a container's state from a specific time without overwriting current data, you must restore it to a new Cosmos DB account or a new resource name within the same account. This creates a separate copy, allowing comparison and validation. The restore timestamp must be within the continuous backup retention window, which is 7 days by default for continuous backup (v2). Performing an in-place restore is incorrect because continuous backup PITR does not support restoring over existing data; it always creates a new resource. Opening a support ticket is unnecessary as PITR is a self-service feature for containers. Rotating account keys is irrelevant to the restore process itself.