Microsoft AZ-400: Azure IaC with Bicep & Terraform
Infrastructure as code is most valuable when it makes environmental change reviewable, repeatable, and recoverable. Azure teams commonly use Bicep or Terraform to…
Read articleEDITORIAL TOPIC / EXAMTOPICS EDITORIAL
Cloud Computing.
Cloud platforms, workload architecture, operations, storage, and infrastructure.
PUBLISHED COVERAGECurated by subject
Microsoft AZ-400: GitHub Actions vs Azure Pipelines
GitHub Actions and Azure Pipelines can both build, test, package, and deploy software to Azure. The useful question is therefore not which product…
Read articleMicrosoft AZ-400: DevSecOps Controls in Azure Delivery Pipelines
DevSecOps is strongest when security becomes part of the delivery decision rather than a report created after software is already in production. Azure…
Read articleMicrosoft AZ-400: Container CI/CD with Azure Container Registry
A container pipeline is reliable only when the image becomes a controlled software artifact instead of a side effect of a build. Azure…
Read articleMicrosoft AZ-400: Blue-Green and Canary Deployments in Azure
Safer Azure releases are not created by choosing a fashionable deployment label. They come from deciding how much change to expose, how quickly…
Read articleMicrosoft AZ-104: Managed Identities for Azure Workloads
Managed identities let Azure workloads authenticate to services that support Microsoft Entra ID without storing an application password, certificate, or account key in…
Read articleMicrosoft AZ-305: Storage Design for High-Scale Azure Applications
Storage design at scale is not a choice between “SQL” and “NoSQL,” nor is it solved by picking the service with the largest…
Read articleMicrosoft AZ-305: Multi-Tenant Identity Design in Azure
Multi-tenant identity design is difficult because the word “tenant” can describe two different things. In a SaaS application, a tenant is usually a…
Read articleMicrosoft AZ-305: Hub-and-Spoke Networking in Azure
Hub-and-spoke networking is one of Azure’s most common enterprise topologies because it separates shared connectivity from workload networks. The hub hosts or connects…
Read articleMicrosoft AZ-305: Hybrid Connectivity to Azure
Hybrid connectivity is not just a network link between an office and a virtual network. It is the path that lets on-premises systems,…
Read articleMicrosoft AZ-305: Highly Available Azure Applications
High availability in Azure is not a single feature that can be enabled after an application is deployed. It is an end-to-end property…
Read articleMicrosoft AZ-305: Azure Landing Zones at Scale
An Azure landing zone is the foundation that lets many workloads use Azure without each team rebuilding identity, networking, governance, security, and operations…
Read articleMicrosoft AZ-305: Cost-Aware Azure Architecture
Cost-aware architecture is not the practice of choosing the cheapest Azure service in every comparison. It is the discipline of designing a workload…
Read articleMicrosoft AZ-305: Azure Governance: Policy, RBAC & Groups
Azure governance works when several controls cooperate without being confused with one another. Management groups organize scope, Azure Policy evaluates resource state, and…
Read articleMicrosoft AZ-305: Azure Disaster Recovery with Paired Regions
Azure disaster recovery becomes more reliable when the secondary region is chosen for a reason rather than because two region names happen to…
Read article