Venture into the world of Azure Infrastructure, where design meets functionality. Harness your skills and gain mastery over complex cloud structures to ace the AZ-305 Designing Microsoft Azure Infrastructure Solutions exam!
Gauge your current knowledge
Gauge your current knowledge
Azure SQL Database is a fully managed relational database service that offers several deployment options to match different workload needs. A single database works best for modern cloud applications that need isolated, predictable performance, while an elastic pool lets multiple databases share a fixed set of resources, which saves money when databases have uneven or unpredictable usage patterns. The hyperscale tier separates compute from storage, allowing the database to grow to 100 TB or more and to scale out read workloads quickly by adding read replicas. The service enforces transactional consistency through ACID properties, so every transaction either completes fully or rolls back entirely, which keeps data accurate. For high availability, Azure SQL Database uses zone-redundant deployments that spread replicas across availability zones and geo-replication that copies data to a paired region; if the primary fails, traffic automatically fails over to a replica. Automated scaling adjusts resources based on workload demand without manual intervention, and backup and restore strategies include automated backups with configurable retention periods and point-in-time restore to recover from user errors or corruption.
Azure SQL Managed Instance bridges the gap between on-premises SQL Server and a fully managed cloud service by offering near-100% compatibility with SQL Server features. This makes it the right choice for organizations that need to lift and shift existing SQL Server databases without rewriting application code or changing T-SQL commands. It supports older SQL Server features such as linked servers, CLR integration, and SQL Server Agent, which many legacy applications depend on. The high-availability architecture mirrors SQL Server's Always On Availability Groups, maintaining multiple synchronous replicas within the same region so that a hardware failure causes no data loss and only seconds of downtime. Backup and restore strategies include automated backups, long-term retention policies, and the ability to restore to any point within the retention window. The service also provides flexible pricing through reserved capacity and hybrid benefit options, which help manage total cost of ownership when migrating existing SQL Server licenses.
Azure Database for PostgreSQL delivers a managed PostgreSQL service that handles deployment, patching, backups, and scaling automatically. It offers strong transactional consistency through PostgreSQL's MVCC (multi-version concurrency control) implementation, which ensures that concurrent transactions see a consistent snapshot of data without locking conflicts. The service provides automated scaling that adjusts compute and storage resources based on performance metrics, so the database can handle workload spikes without manual intervention. For high availability, it supports zone-redundant configurations that replicate data synchronously across availability zones, and read replicas that offload reporting or analytics queries from the primary instance. Backup and restore strategies include automated backups with up to 35 days of retention and geo-redundant storage options that protect against regional disasters by storing backups in a paired Azure region.
Azure Database for MySQL provides a fully managed MySQL service designed for applications that need high availability, security, and predictable performance. It enforces transactional consistency using ACID properties and MySQL's InnoDB storage engine, which handles row-level locking and crash recovery. The service offers multiple high-availability options, including zone-redundant deployments that keep synchronous replicas in separate availability zones and read replicas that distribute read traffic across multiple copies. Automated scaling adjusts storage and compute resources based on workload demands, and the service includes built-in connection pooling to handle large numbers of concurrent connections efficiently. The total cost of ownership is lower than running MySQL on virtual machines because the managed service eliminates administrative overhead for patching, backups, and hardware maintenance, and reserved capacity pricing provides additional discounts for predictable workloads.
Choosing the right Azure relational database requires evaluating several factors together rather than in isolation. Workload patterns determine the deployment model: single databases suit independent applications, elastic pools suit multi-tenant SaaS applications with variable usage, and hyperscale suits large-scale OLTP workloads with high throughput requirements. Consistency requirements are largely satisfied by all services through ACID compliance, but the specific isolation level and locking behavior differ between SQL Server, PostgreSQL, and MySQL, so applications that depend on database-specific concurrency behavior may need to stay with their native platform. High-availability architectures differ in recovery time and data loss tolerance: zone-redundant deployments protect against datacenter failures within a region, while geo-replication protects against regional disasters but introduces replication lag. Scalability options include vertical scaling (increasing compute and storage) and horizontal scaling (adding read replicas), but only Azure SQL Database's hyperscale tier separates compute from storage to allow near-instant scaling of compute resources. Cost constraints should account for compute, storage, backup storage, and data egress charges, and reserved capacity or hybrid benefit options can reduce costs for predictable workloads.
StudyCerts
StudyCerts