This is the perfect question to really see if the two of you are a match.He loves fast cars, and you enjoy slow bike rides- maybe not so much of a match.In such scenario, a DBA can look at recovery_vlf_count and log_recovery_size_mb to understand the number of vlfs to recover and log size to recover if the database is restarted.
On the other hand, this could reveal he’s a family man depending on his answer.4.
Every once in a while, a DBA faces a situation where a user has a long running transaction in killed\rollback state causing blocking issue.
Shrinking your transaction log file often can lead to disk fragmentation and reduce your disk throughput and performance.
Most DBAs today operating their SQL Server database in full recovery model, schedule their transaction log backups to recur on a specific time interval (every 15 mins) for a highly transactional database to avoid autogrowth of the transaction log files.
This works well assuming transactional activity is consistent or predictable throughout the time interval, producing transaction log backup files of equal size with no autogrows.