Cloud & Architecture
Amazon AWS SAA-C03: Disaster Recovery Patterns on AWS
AWS disaster recovery architecture is a tradeoff between recovery time objective, recovery point objective, cost, operational complexity, data consistency, and how much infrastructure remains active before a disaster. AWS Well-Architected currently describes four common strategies: backup and restore, pilot light, warm standby, and multi-Region active-active. These are not maturity levels every workload must climb. Each strategy is appropriate only when its cost and complexity match the business recovery requirement. Home/Amazon/Amazon AWS SAA-C03: Disaster Recovery Patterns on AWSAmazonPublished October 7, 2026On this pageStart with business RTO and RPOUse pilot light for…
Amazon AWS SAA-C03: Decoupling Workloads with SQS
Amazon SQS decouples producers from consumers by giving them a durable queue between request creation and processing. The producer does not need the worker to be available at the same moment; the worker can process at its own pace, scale horizontally, retry transient failures, and survive temporary downstream outages. This simple buffer can remove synchronous dependencies from web requests, batch pipelines, image processing, integration work, and other distributed systems. Home/Amazon/Amazon AWS SAA-C03: Decoupling Workloads with SQSAmazonPublished October 7, 2026On this pageUse Standard queues for scalable independent workSet visibility timeout from…
Amazon AWS SAA-C03: Control Tower for Growing Environments
AWS Control Tower provides a managed way to establish and govern a multi-account AWS environment on top of AWS Organizations. It creates or integrates landing-zone components, applies controls, supports governed organizational units, and provides account provisioning workflows through Account Factory. The value is consistency: new accounts can inherit organization structure, central logging, security roles, control baselines, and identity integration without every platform team rebuilding those foundations manually. Home/Amazon/Amazon AWS SAA-C03: Control Tower for Growing EnvironmentsAmazonPublished October 7, 2026On this pageStart with AWS OrganizationsUse controls by behaviorUse Account Factory for repeatable…
Amazon AWS SAA-C03: AWS Organizations Design Patterns
AWS Organizations is the foundation for governing a multi-account AWS environment. It provides the organization root, organizational units, member accounts, consolidated billing, delegated administration, and policy types such as service control policies. For an Amazon AWS SAA-C03 candidate, the architecture challenge is not creating the organization. It is designing an OU and account model that can support security, workload autonomy, cost ownership, compliance, and service delegation without turning the management account into the place where every cloud task must be performed. Home/Amazon/Amazon AWS SAA-C03: AWS Organizations Design PatternsAmazonPublished October 7,…
Microsoft AZ-104: Azure Arc and Hybrid Windows Server Management
Home/Certifications/Microsoft/Azure Arc and Hybrid Windows Server ManagementCloud & ArchitectureUpdated October 10, 2026 · 7 min readA Windows Server does not have to run in Azure to appear in an Azure management inventory. Azure Arc-enabled servers register supported on-premises or other-cloud machines as Azure resources while the operating system and its applications remain where they are. The operational challenge is deciding what Azure should manage, what stays under local server administration and how to keep the two control planes from contradicting one another.On this pageDecide what Arc changes—and what it does…
Microsoft AZ-104: Azure Virtual WAN Design Decisions
Home/Certifications/Microsoft/Azure Virtual WAN Design Decisions Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Azure Virtual WAN reduces some of the manual routing and connectivity work in a distributed network, but it introduces a managed hub control plane with its own route association, propagation, inspection and cost model. Evaluate it against the actual branch and workload architecture before replacing a functioning hub-and-spoke network. Managed transit can reduce repetitive hub configuration, but a change in route association or propagation can alter traffic across many branches. Evaluate Virtual WAN with explicit…
Microsoft AZ-104: Azure VPN Gateway Design
Home/Certifications/Microsoft/Microsoft AZ-104: Azure VPN Gateway Design Cloud & ArchitectureUpdated October 10, 2026 · 7 min read A VPN Gateway design succeeds when the required networks exchange routes securely and recover predictably from tunnel, device or gateway failures. Picking a gateway SKU is only one part of planning authentication, routing, resilience and operations. A working VPN tunnel is only the beginning of connectivity. Engineers must validate advertised routes, overlapping address ranges, authentication choices, gateway redundancy, and the behavior users see when one peer or circuit fails. On this pageChoose the connection…
Microsoft AZ-104: Azure Subscription Design
Home/Certifications/Microsoft/Microsoft AZ-104: Azure Subscription Design Cloud & ArchitectureUpdated October 10, 2026 · 7 min read An Azure subscription is simultaneously a deployment scope, a governance boundary and a unit with billing and service limits. Good subscription design makes those boundaries deliberate without turning every application team into an isolated platform operator. Subscription boundaries should reflect governance, operational ownership, service limits, and cost allocation rather than every application name. A good design lets shared networking and security controls apply consistently without creating needless cross-subscription dependencies. On this pageStart with the purpose…
Microsoft AZ-104: Azure Resource Locks
Home/Certifications/Microsoft/Microsoft AZ-104: Azure Resource Locks Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Azure resource locks are guardrails against accidental management operations, not a replacement for least-privilege access, backups or recovery planning. Knowing precisely what a lock blocks—and what it does not—is essential before applying one to a production estate. A delete lock may prevent one management operation while leaving data-plane behavior and other forms of loss unaffected. Test the intended protection with a representative resource and document how an authorized operator removes it during maintenance. On this…
Microsoft AZ-104: Azure Management Groups
Home/Certifications/Microsoft/Microsoft AZ-104: Azure Management Groups Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Management groups let a large Azure estate apply governance above individual subscriptions. The hard design problem is not creating folders in a hierarchy; it is placing subscriptions so inherited access and policy match how the organization actually operates. A hierarchy that mirrors an organization chart too closely can make policy and role inheritance harder to manage after a reorganization. Group subscriptions where governance requirements genuinely differ, and test effective policy at the destination scope. On…
Microsoft AZ-104: Hybrid Identity Decisions
Home/Certifications/Microsoft/Microsoft AZ-104: Hybrid Identity Decisions Cloud & ArchitectureUpdated October 10, 2026 · 7 min read Hybrid identity is a decision about where account attributes originate, how sign-ins are verified and which synchronization or provisioning service owns each object. Reliable Azure administration requires distinguishing identity sources and authentication paths before choosing a synchronization agent. An on-premises account can synchronize to Microsoft Entra without using the same authentication path for every application. Clarify the authoritative attribute source, provisioning method, sign-in flow, and exception process before deploying a connector. On this pageSeparate directory…
Microsoft AZ-104: Azure Front Door vs. Application Gateway
Home/Certifications/Microsoft/Azure Front Door vs. Application Gateway Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Azure Front Door and Application Gateway both route HTTP traffic, but they operate at different points in a request’s journey. The right choice depends on global reach, regional network boundaries, origin exposure, failure domains and the kind of traffic the application actually serves. An application with users across continents has different entry-point needs from a private regional workload. Origin reachability, web application filtering, health probes, and failover routes should decide whether a global front…
Microsoft AZ-104: FSLogix Profiles for Azure Virtual Desktop
Home/Certifications/Microsoft/FSLogix Profiles for Azure Virtual Desktop Cloud & ArchitectureUpdated October 10, 2026 · 6 min read FSLogix profile containers can make pooled Azure Virtual Desktop sessions feel persistent, but an apparently simple VHDX attachment depends on identity, file-share permissions, network access and a clean session lifecycle. Operational evidence matters more than a successful initial sign-in. Profile containers depend on more than file-share capacity. In a pooled desktop fleet, attachment rights, network reachability, lock behavior, and sign-out cleanup determine whether a user resumes with the expected settings rather than a temporary…
Microsoft AZ-104: ExpressRoute Resilience Patterns
Home/Certifications/Microsoft/ExpressRoute Resilience Patterns Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Private connectivity can be reliable and still contain one unexpected point of failure. ExpressRoute resilience depends on physical diversity, independent routing paths and tested failover behavior—not simply the presence of two BGP sessions on a circuit. Redundant sessions across one physical location may still share a provider or facility failure. ExpressRoute resilience should be assessed through independent circuits, peering, routing choices, and a controlled test of the exact failure the design must survive. On this pageDistinguish link…
Microsoft AZ-104: Azure Backup and Recovery Design
Home/Certifications/Microsoft/Microsoft AZ-104: Azure Backup and Recovery Design Cloud & ArchitectureUpdated October 10, 2026 · 6 min read A useful Azure recovery design starts with what the business must restore, how much data it can lose and who can authorize recovery. Selecting a vault is one important step, but it does not establish that a damaged application can return to service. Restoring a database copy is not the same as restoring a working business service. Document which dependencies return first, how access is re-established, what the recovery objective means, and how…