Q: 9
You are the DBA of your organization. You provided a cloned instance from the production Cloud SQL
for PostSQL database to the developers for testing purposes. After the creation of the clone. Your
developers notice missing data in one of the recently altered tables. What should you do to ensure
that all data in included?
Options
Discussion
C
Had something like this in a mock, C fits best. PITR will include all changes up to a specific point, so any recent alters or missing data should be covered. Dumps can miss new data if not timed right. Pretty sure C is what they want here, but open if someone spots a detail I missed.
I think C. Using PITR ensures all changes, including recent alters, are included in the cloned instance. Dumps or backups might miss new data if taken before the change. Let me know if someone sees a catch here, but this matches what I’ve seen in practice.
A is off here, C is what you need since PITR ensures all latest changes are included in the clone.
C vs D but I'm confident it's C. PITR will let you restore the clone after all recent changes, including any ALTERs, so you catch new data. D is a common distractor unless unlogged tables were involved, which isn’t specified here.
It’s C here. PITR means you can clone the current production database to a state after any recent table alterations, so you don’t miss data added or changed after the initial clone. D looks tempting but only matters if those tables were UNLOGGED, which isn’t stated. Seen similar question in practice sets.
Option D
C vs D here, but pretty sure C is right. PITR gets all the latest changes after table alters, while D's focus on unlogged tables is a bit of a trap in this scenario. Seen similar advice in practice sets, but open if anyone disagrees.
C tbh. Using PITR with a fresh clone will pull in all the recent changes, including those new table alterations and data that might’ve been missed before. Standard dumps or older backups could leave out recent stuff. Someone correct me if I’m missing something obvious!
Not sure C or D, but leaning C.
Be respectful. No spam.
