{"id":68237,"date":"2026-09-23T09:33:40","date_gmt":"2026-09-23T09:33:40","guid":{"rendered":"https:\/\/www.eccentrix.ca\/?p=68237"},"modified":"2026-09-23T10:46:12","modified_gmt":"2026-09-23T10:46:12","slug":"transition-from-az-104-to-az-305","status":"publish","type":"post","link":"https:\/\/www.eccentrix.ca\/en\/eccentrix-corner\/az-104-to-az-305\/","title":{"rendered":"AZ-104 to AZ-305: what changes when you move from operator to architect"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"68237\" class=\"elementor elementor-68237 elementor-65544\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1a96984f e-flex e-con-boxed e-con e-parent\" data-id=\"1a96984f\" data-element_type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-d5a4c97 elementor-widget elementor-widget-heading\" data-id=\"d5a4c97\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Introduction<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-4e9eab47 elementor-widget elementor-widget-text-editor\" data-id=\"4e9eab47\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>AZ-104 makes you valuable because you know how to operate Azure. AZ-305 makes you valuable because you know how to design Azure so that it can be operated by teams\u2014at scale, under constraints, and without constant crisis management.<\/p><p>This is not just a step up to a &#8220;harder exam.&#8221;The transition from AZ-104 to AZ-305 represents a professional step up.<\/p><p>Below is what changes when you transition from operator to architect: responsibilities, mindsets, deliverables, and the errors that surface first in the real world.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-3889cf1 elementor-widget elementor-widget-heading\" data-id=\"3889cf1\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">1) Your scope is expanding: from underwriting tasks to organizational systems.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2278df5 elementor-widget elementor-widget-text-editor\" data-id=\"2278df5\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>As an AZ-104 operator, your scope typically covers:<\/p><ul><li>a subscription or a set of resource groups<\/li><li>a specific workload or platform component<\/li><li>day-to-day stability and incident response<\/li><li>accuracy of implementation and configuration<\/li><\/ul><p>As an AZ-305 architect, your scope shifts to:<\/p><ul><li>multiple subscriptions and environments (dev\/test\/prod)<\/li><li>multiple teams with varying levels of maturity<\/li><li>shared services (identity, networking, monitoring, governance)<\/li><li>long-term maintainability and cost predictability<\/li><li>risk management (security, compliance, resilience)<\/li><\/ul><p>In other words: you stop thinking &#8220;how do I deploy this?&#8221; and start thinking &#8220;how do I deploy this in a repeatable, secure, and consistent way over the long term?&#8221;<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d8ecc5c elementor-widget elementor-widget-heading\" data-id=\"d8ecc5c\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">2) Your mindset shifts: from execution to making trade-offs.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e978d44 elementor-widget elementor-widget-text-editor\" data-id=\"e978d44\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Operators execute. Architects decide. This means you become responsible for making trade-offs such as:<\/p><ul><li>speed vs. control (self-service vs. approvals\/guardrails)<\/li><li>cost vs. resilience (single region vs. multi-region, RTO\/RPO choices)<\/li><li>simplicity vs. flexibility (standard models vs. exceptions)<\/li><li>security vs. ease of use (strict boundaries vs. user friction)<\/li><li>centralization vs. autonomy (platform team vs. product teams)<\/li><\/ul><p>The architect\u2019s role is not to choose the &#8220;best&#8221; option in the absolute sense. It is to choose the right option given the constraints, and to document the reasoning.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-52b4309 elementor-widget elementor-widget-heading\" data-id=\"52b4309\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">3) You shift from \"managing incidents\" to \"designing to prevent incidents.\"<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-705ab83 elementor-widget elementor-widget-text-editor\" data-id=\"705ab83\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>AZ-104 work often looks like this:<\/p><ul><li>diagnosing<\/li><li>mitigating<\/li><li>restoring service<\/li><li>improving monitoring<\/li><li>fixing the root cause<\/li><\/ul><p>AZ-305 work looks like this:<\/p><ul><li>preventing a class of failures from recurring<\/li><li>standardizing models that reduce drift<\/li><li>building guardrails that block risky deployments early<\/li><li>integrating operational responsibility into the architecture<\/li><\/ul><p>Architects do not eliminate incidents. They eliminate surprises.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a5dd235 elementor-widget elementor-widget-heading\" data-id=\"a5dd235\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">4) Your deliverables are changing: from runbooks to architecture artifacts.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-28554e7 elementor-widget elementor-widget-text-editor\" data-id=\"28554e7\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Typical AZ-104 deliverables (implementation outputs):<\/p><ul><li>deployed and configured resources<\/li><li>monitoring rules\/dashboards<\/li><li>backup configuration + restore procedures<\/li><li>operational runbooks (e.g., key rotation, recovery steps)<\/li><li>incident notes and remediation actions<\/li><\/ul><p>Typical AZ-305 deliverables (design\/decision outputs):<\/p><ul><li>reference architecture diagrams + rationale<\/li><li>landing zone design (management group hierarchy, subscriptions, policy strategy)<\/li><li>network topology decisions (hub-and-spoke\/vWAN, DNS, egress control)<\/li><li>identity and access model (RBAC strategy, PIM approach, boundaries)<\/li><li>resilience plan (zones\/regions, DR approach, RTO\/RPO targets)<\/li><li>security logging strategy (what to log, where, who monitors)<\/li><li>cost model assumptions + guardrails<\/li><li>Architecture Decision Records (ADRs)<\/li><\/ul><p>If you aren&#8217;t producing these artifacts, you aren&#8217;t truly operating in an architect role; you&#8217;re just a &#8220;senior admin with opinions.&#8221;<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-f75a007 elementor-widget elementor-widget-heading\" data-id=\"f75a007\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">5) The \"what breaks first\" list (operator \u2192 architect reality)\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d7e403f elementor-widget elementor-widget-text-editor\" data-id=\"d7e403f\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Here is what typically breaks first when someone moves to this architecture without changing their mindset:<\/p><p><strong>Network complexity and DNS<\/strong><\/p><ul><li>routing assumptions fail in hybrid setups<\/li><li>private endpoints break name resolution<\/li><li>egress control is inconsistent across environments<\/li><li>&#8220;it works in dev&#8221; fails in prod due to differing paths or policies<\/li><\/ul><p><strong>Identity boundaries and access sprawl<\/strong><\/p><ul><li>too many Owners<\/li><li>unclear separation of duties<\/li><li>service principals with unmanaged secrets<\/li><li>no time-bound privileged access<\/li><\/ul><p><strong>At-scale governance<\/strong><\/p><ul><li>policies applied too late (after sprawl has set in)<\/li><li>exceptions become permanent<\/li><li>naming\/tagging not enforced, causing a collapse in cost and operational visibility<\/li><\/ul><p><strong>Theoretical resilience<\/strong><\/p><ul><li>backups exist, but restores are untested<\/li><li>DR steps are manual and undocumented<\/li><li>single-region dependencies lurk within &#8220;multi-region&#8221; designs<\/li><\/ul><p><strong>Unclear operational responsibility<\/strong><\/p><ul><li>no one knows who owns shared components<\/li><li>changes made without change control<\/li><li>noisy or incomplete monitoring, leading to slower incident response<\/li><\/ul><p>Architects succeed by designing for these failure modes from the start.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-c2a1f91 elementor-widget elementor-widget-heading\" data-id=\"c2a1f91\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">6) How to tell if you have made the change (quick self-test)<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-4150c60 elementor-widget elementor-widget-text-editor\" data-id=\"4150c60\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>You are still thinking like an operator if you focus primarily on:<\/p><ul><li>&#8220;how to configure X&#8221;<\/li><li>&#8220;which service is best suited&#8221;<\/li><li>&#8220;how to troubleshoot issues related to Y&#8221;<\/li><\/ul><p>You are thinking like an architect when you consistently ask the following questions:<\/p><ul><li>&#8220;what are the requirements and constraints?&#8221;<\/li><li>&#8220;what is the failure mode?&#8221;<\/li><li>&#8220;who handles operations at 2 a.m.?&#8221;<\/li><li>&#8220;how can this be established as a standard?&#8221;<\/li><li>&#8220;what are the costs and the governance model?&#8221;<\/li><li>&#8220;what is the rollback plan?&#8221;<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7b65079 elementor-widget elementor-widget-heading\" data-id=\"7b65079\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">A pragmatic approach: building credibility, then formalizing an architectural vision.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-b35b6a0 elementor-widget elementor-widget-text-editor\" data-id=\"b35b6a0\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p><span style=\"font-weight: 400;\">A strong operator foundation (acquired through the <\/span><a href=\"https:\/\/www.eccentrix.ca\/en\/courses\/microsoft\/azure\/microsoft-certified-azure-administrator-associate-az104\/\"><span style=\"font-weight: 400;\">AZ-104<\/span><\/a><span style=\"font-weight: 400;\"> training) makes your architecture decisions real. The <\/span><a href=\"https:\/\/www.eccentrix.ca\/en\/courses\/microsoft\/azure\/microsoft-certified-azure-solutions-architect-expert-az104-305\/\"><span style=\"font-weight: 400;\">AZ-305<\/span><\/a><span style=\"font-weight: 400;\"> training formalizes the cross-domain design skills that organizations need: identity, networking, governance, and resilience.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a76984c elementor-widget elementor-widget-heading\" data-id=\"a76984c\" data-element_type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">FAQ<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7a5c4f7 elementor-widget elementor-widget-accordion\" data-id=\"7a5c4f7\" data-element_type=\"widget\" data-widget_type=\"accordion.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"elementor-accordion\">\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<h6 id=\"elementor-tab-title-1281\" class=\"elementor-tab-title\" data-tab=\"1\" role=\"button\" aria-controls=\"elementor-tab-content-1281\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><svg class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><svg class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Do I need to \"stop all technical work\" to become an architect?<\/a>\n\t\t\t\t\t<\/h6>\n\t\t\t\t\t<div id=\"elementor-tab-content-1281\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"1\" role=\"region\" aria-labelledby=\"elementor-tab-title-1281\"><p>No. The best architects maintain enough technical practice to understand operational realities. The shift lies in the responsibility for decisions, not in abandoning execution.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<h6 id=\"elementor-tab-title-1282\" class=\"elementor-tab-title\" data-tab=\"2\" role=\"button\" aria-controls=\"elementor-tab-content-1282\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><svg class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><svg class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Is the AZ-305 certification intended only for enterprise environments?<\/a>\n\t\t\t\t\t<\/h6>\n\t\t\t\t\t<div id=\"elementor-tab-content-1282\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"2\" role=\"region\" aria-labelledby=\"elementor-tab-title-1282\"><p>No. Even small environments require architectural consideration\u2014particularly regarding governance, identity boundaries, and resilience\u2014because small teams cannot afford chaos.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<h6 id=\"elementor-tab-title-1283\" class=\"elementor-tab-title\" data-tab=\"3\" role=\"button\" aria-controls=\"elementor-tab-content-1283\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><svg class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><svg class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">What's the quickest way to adopt an architect's mindset?<\/a>\n\t\t\t\t\t<\/h6>\n\t\t\t\t\t<div id=\"elementor-tab-content-1283\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"3\" role=\"region\" aria-labelledby=\"elementor-tab-title-1283\"><p>Start by documenting the trade-offs and decisions made, and ensure that each design incorporates:<\/p><ul><li>an identity model<\/li><li>a network\/DNS model<\/li><li>governance guardrails<\/li><li>resilience objectives and tested recovery procedures<\/li><\/ul><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t<div class=\"elementor-accordion-item\">\n\t\t\t\t\t<h6 id=\"elementor-tab-title-1284\" class=\"elementor-tab-title\" data-tab=\"4\" role=\"button\" aria-controls=\"elementor-tab-content-1284\" aria-expanded=\"false\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon elementor-accordion-icon-left\" aria-hidden=\"true\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-closed\"><svg class=\"e-font-icon-svg e-fas-plus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H272V64c0-17.67-14.33-32-32-32h-32c-17.67 0-32 14.33-32 32v144H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h144v144c0 17.67 14.33 32 32 32h32c17.67 0 32-14.33 32-32V304h144c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<span class=\"elementor-accordion-icon-opened\"><svg class=\"e-font-icon-svg e-fas-minus\" viewBox=\"0 0 448 512\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\"><path d=\"M416 208H32c-17.67 0-32 14.33-32 32v32c0 17.67 14.33 32 32 32h384c17.67 0 32-14.33 32-32v-32c0-17.67-14.33-32-32-32z\"><\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t<a class=\"elementor-accordion-title\" tabindex=\"0\">Is there a reference list of Microsoft certification paths?<\/a>\n\t\t\t\t\t<\/h6>\n\t\t\t\t\t<div id=\"elementor-tab-content-1284\" class=\"elementor-tab-content elementor-clearfix\" data-tab=\"4\" role=\"region\" aria-labelledby=\"elementor-tab-title-1284\"><p>Yes, Microsoft frequently publishes updates to available <a href=\"https:\/\/arch-center.azureedge.net\/Credentials\/Certification-Poster_en-us.pdf\" target=\"_blank\" rel=\"noopener\">certification paths<\/a> in the form of a digital poster.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Introduction AZ-104 makes you valuable because you know how to operate Azure. AZ-305 makes you valuable because you know how to design Azure so that it can be operated by teams\u2014at scale, under constraints, and without constant crisis management. This is not just a step up to a &#8220;harder exam.&#8221;The transition from AZ-104 to AZ-305 [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":68223,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jet_sm_ready_style":"","_jet_sm_style":"","_jet_sm_controls_values":"","_jet_sm_fonts_collection":"","_jet_sm_fonts_links":"","footnotes":""},"categories":[84],"tags":[159,104],"class_list":["post-68237","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-eccentrix-corner","tag-cloud","tag-microsoft-azure"],"_links":{"self":[{"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/posts\/68237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/comments?post=68237"}],"version-history":[{"count":6,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/posts\/68237\/revisions"}],"predecessor-version":[{"id":68246,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/posts\/68237\/revisions\/68246"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/media\/68223"}],"wp:attachment":[{"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/media?parent=68237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/categories?post=68237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eccentrix.ca\/en\/wp-json\/wp\/v2\/tags?post=68237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}