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 offers several managed relational services that maintain transactional consistency through ACID properties. Azure SQL Database is a fully managed cloud database that runs without administrative patching, offering single database deployments for independent applications and elastic pools to share resources among multi-tenant workloads. For existing SQL Server migrations, Azure SQL Managed Instance provides near-100% compatibility with legacy database engine features, allowing organizations to lift-and-shift databases without rewriting application code. For open-source architectures, Azure Database for PostgreSQL uses multi-version concurrency control to handle simultaneous queries, while Azure Database for MySQL leverages the InnoDB engine to manage row-level locking. Choosing the correct database platform depends on application dependency on native database engines, desired isolation levels, and migration requirements.
Workload patterns such as transaction volume, concurrency, and I/O throughput determine the selection of the service and compute tiers. The General Purpose tier uses a remote storage model that separates compute and storage layers, offering a choice between a provisioned compute tier or an automatic serverless compute tier that scales based on demand. The Business Critical tier places local SSD storage directly on the compute nodes to minimize latency, offering high availability with read scale-out replicas. The Hyperscale tier utilizes a cloud-native architecture that scales database storage up to 128 TB dynamically by separating the compute, page server, and log rate layers. Selecting a tier requires evaluating performance requirements against costs, choosing between the vCore model for independent resource tuning and the DTU model for pre-configured bundles.
Scalability solutions must dynamically adapt to changing demand to maintain application performance. Vertical scaling, or scaling up and down, increases or decreases compute resources by adjusting vCores or moving databases to higher service tiers without modifying database architecture. Horizontal scaling, or scaling out and in, adds or removes database instances to distribute workload volume. This horizontal approach uses elastic pools to balance shared resources across multiple databases, sharding to split large tables across database instances, and read replicas to offload read-heavy traffic from the primary write database. Dynamic scaling can be initiated manually by administrators or automatically handled by the database system within a serverless tier to match real-time workload behavior.
Data protection strategies secure relational databases at rest, in transit, and during active use. Transparent Data Encryption (TDE) encrypts physical database files, log files, and backups at rest using keys managed by Azure or custom keys stored in Azure Key Vault. To protect sensitive fields from database administrators, Always Encrypted performs client-side encryption using a driver so that plaintext keys never reach the database engine. Dynamic Data Masking protects sensitive information inline by obscuring query results on the fly without changing the underlying physical data. Finally, Azure Defender for SQL continuously monitors the system to run vulnerability assessments and detect active security threats like SQL injection attacks.
Azure Cosmos DB is a globally distributed, multi-model database designed to store semi-structured JSON data. Applications interact with Cosmos DB using specialized APIs, including the SQL API for document queries, the MongoDB API for migration compatibility, and other options like the Cassandra API and Gremlin API. To distribute data evenly and avoid performance hotspots, developers must choose a high-cardinality partition key that governs how physical partitions store the records. Throughput is provisioned using Request Units (RUs), which can be scaled manually, configured to autoscale, or run in a serverless mode for unpredictable traffic. Consistency levels range from strong consistency for immediate replication to eventual consistency for low-latency, high-throughput reads.
Unstructured data requires specialized storage services depending on access frequency, scalability, and analytical processing needs. Azure Blob Storage is an object storage service designed for massive, flat namespaces, utilizing hot, cool, and archive storage tiers to lower costs based on access patterns. Azure Data Lake Storage Gen2 builds on top of Blob Storage by adding a hierarchical namespace that organizes files into traditional folder directories to accelerate big data analytics engines. For global applications requiring millisecond write speeds for unstructured metadata, Azure Cosmos DB can host unstructured records globally, though it has higher operational costs. Choosing between these systems depends on whether the workload requires low-cost files, structured folder hierarchies, or global transactional performance.
Balancing architecture features against cost requires analyzing the access frequency and performance targets of your data. Azure Blob Storage fits simple file retrieval without complex queries, allowing users to save money by moving unused data to colder storage tiers. Azure Data Lake Storage Gen2 is the ideal choice for big data analytics because its folder structures prevent analytics engines from scanning irrelevant data. Azure Cosmos DB provides global low-latency reads and writes for real-time applications but requires careful throughput tuning to manage costs. Designers must evaluate transaction consistency, query complexity, and geographic distribution requirements to justify the expense of premium tiers.
Data durability and protection rely on physical redundancy, logical locks, and recovery policies. To protect against local failures, Zone-Redundant Storage (ZRS) replicates data across three availability zones, while Geo-Redundant Storage (GRS) copies data asynchronously to a secondary region. Immutable Blob Storage Policies protect data by placing it in a write-once, read-many state, while soft delete and snapshots allow recovery of deleted files. Azure Backup orchestrates long-term retention policies inside Recovery Services vaults, which must have their storage replication type chosen before initializing backups. During a regional outage, administrators evaluate the last synchronization time property of the storage account to calculate potential data loss before triggering a failover.
Designing data integration solutions involves orchestrating data flow between relational, semi-structured, and unstructured storage environments. Azure Data Factory acts as a centralized data integration service that extracts data from source boundaries, transforms it, and loads it into target data stores. Security policies must be applied at integration boundaries, utilizing private endpoints to keep data pipelines within isolated network limits. Dependencies between data pipelines are managed through structured control flows, ensuring that data ingestion from IoT devices or transactional databases occurs in the correct order before analytics services process the information. Choosing the proper integration method depends on the required latency, the volume of data being moved, and the computational complexity of the data transformations.
Azure SQL Database is a fully managed relational database service that runs in the cloud without you needing to manage servers or apply patches. It offers several deployment options that fit diffe…
Azure SQL Database is a fully managed relational database service that runs in the cloud without you needing to manage servers or apply patches. It offers several deployment options that fit diffe…
When you design a data integration solution on Azure, you choose among three primary services: Azure Data Factory (ADF) , Azure Synapse Analytics Pipelines, and Azure Logic Apps. Each serv…
When you design a data integration solution on Azure, you choose among three primary services: Azure Data Factory (ADF) , Azure Synapse Analytics Pipelines, and Azure Logic Apps. Each serv…
Azure Cosmos DB is a globally distributed, multi-model database service built for handling semi-structured data such as JSON documents. It provides automatic indexing, rich query capabilities, and…
Azure Cosmos DB is a globally distributed, multi-model database service built for handling semi-structured data such as JSON documents. It provides automatic indexing, rich query capabilities, and…
StudyCerts
StudyCerts