A logical SQL server is a management and connection boundary for Azure SQL Database, not a virtual machine that you patch directly. Merrow Dispatch needs a database configuration that operations can read back without confusing that logical server with the application's compute tier.
Choose the database tier and capacity from the supplied workload requirements, then review zone redundancy and recovery separately. Increasing capacity does not create an application authorization policy, and a redundancy setting does not reverse an accidental delete. Here you create and update local database configuration. The simulator does not execute SQL, benchmark query performance, provision replicas, or validate region-specific production tier availability. Treat the supplied capacity values as fictional training requirements. The final decisions ask what evidence would still be needed before an actual workload could rely on those settings.
Configure the logical database and name the remaining workload proof.