Explanation
According to the Veeam Agent for Microsoft Windows User Guide1, you need to enable application-aware processing to ensure quiescence of the SQL databases during the backup. Application-aware processing allows Veeam Agent for Microsoft Windows to create transactionally consistent backups of SQL Server VMs.

To achieve the goal of recovering a single SQL Database in a consistent manner with minimal impact on the production environment during production hours, while allowing for granular restores through the Veeam console, the engineer should A: Schedule transaction log processing every 30 minutes. By enabling application-aware processing for the SQL VM and scheduling the main backup job to run every 24 hours, the base image of the SQL database is protected. However, to achieve a more granular Recovery Point Objective (RPO) and ensure the ability to restore to specific points in time, transaction log backups must be performed more frequently. Configuring the backup job to process transaction logs every 30 minutes captures the SQL database changes more frequently without the overhead of a full backup, allowing for point-in-time restores directly from the Veeam console without the need for SQL Management Studio (SSMS) or a Database Administrator (DBA). This setup aligns with the goals of maintaining operational efficiency and minimizing the impact on production while ensuring robust data protection capabilities.

After using Instant VM Recovery to bring a critical crashed server back online quickly, the final step required to complete the recovery process is A: Migrate to production. Instant VM Recovery allows a VM to run directly from the backup file in a temporary location, enabling rapid recovery and minimal downtime.
However, because the VM is running in this provisional state, it's essential to migrate it back to the production environment to ensure long-term stability and performance. The "Migrate to production" operation involves moving the running VM from the backup storage to the production storage, typically involving a storage vMotion in VMware environments or a similar process in other hypervisors. This step ensures that the VM is fully restored to its original or a new production environment, solidifying the recovery and allowing the VM to operate as part of the normal infrastructure once again.

Explanation
https://helpcenter.veeam.com/docs/backup/vsphere/staged_restore_about.html?ver=120