Q: 19
You released a popular mobile game and are using a 50 TB Cloud Spanner instance to store game
data in a PITR-enabled production environment. When you analyzed the game statistics, you realized
that some players are exploiting a loophole to gather more points to get on the leaderboard. Another
DBA accidentally ran an emergency bugfix script that corrupted some of the data in the production
environment. You need to determine the extent of the data corruption and restore the production
environment. What should you do? (Choose two.)
Options
Discussion
Nah, it's not D here. A and E are correct because backup/restore is for big corruption (A), while stale read/write (E) is best for smaller bits. Easy to mix up since D looks tempting, but pretty sure it's wrong.
Maybe A and E, but not totally sure since B seems close too. Just going with what matches the docs and the split by "extent of corruption."
For this type of scenario, you'd usually go with A and E. If the corruption is big, the backup/restore process is necessary, but for minor or isolated issues, you can do a stale read at a safe timestamp and just overwrite those rows. If it wasn't asking about extent and wanted full restore every time, then D would be worth considering, but that's not what it says here. Pretty sure about this split-any objections?
A, E tbh. Similar question is in official practice and Spanner docs are clear on restore options.
Maybe A and E. Had something like this in a mock, both options fit for significant and minor corruption.
Be respectful. No spam.
