Differences

This shows you the differences between two versions of the page.

--- certification:azure-foundational [2024/03/10 18:25] – skipidar
+++ certification:azure-foundational [2024/09/05 19:48] (current) – skipidar
@@ Line 4: / Line 4: @@
 https://learn.microsoft.com/en-us/credentials/certifications/exams/az-900/
+Exam AZ-303: Microsoft Azure Architect
+https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RE4psD6
 Azure for AWS
@@ Line 47: / Line 50: @@
 https://www.bdrsuite.com/blog/network-security-groups-aws-azure-brief-overview/#:~:text=Unlike%20the%20AWS%20security%20group,attached%20to%20VMs%20(Resource%20Manager)
-=== Network ===
-== public / private subnets ==
-Comparison of AWS public / private subnets
-with Azure: https://devblogs.microsoft.com/premier-developer/differentiating-between-azure-virtual-network-vnet-and-aws-virtual-private-cloud-vpc/
-{{https://s3.eu-central-1.amazonaws.com/alf-digital-wiki-pics/sharex/QxvMzFbgxl.png}}
-  * https://learn.microsoft.com/en-us/azure/virtual-network/tutorial-filter-network-traffic
-{{https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/media/default-outbound-access/explicit-outbound-options.png}}
-see Default outbound access in Azure https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access
@@ Line 108: / Line 95: @@
 ==== Knowhow ====
-=== Azure physical infrastructure ===
-https://learn.microsoft.com/en-us/training/modules/describe-core-architectural-components-of-azure/5-describe-azure-physical-infrastructure
-== Availability Zones ==
-{{https://learn.microsoft.com/en-us/training/wwl-azure/describe-core-architectural-components-of-azure/media/availability-zones-c22f95a3.png}}
-== Region pairs ==
-  * Planned Azure updates are rolled out to paired regions one region at a time to minimize downtime and risk of application outage.
-{{https://learn.microsoft.com/en-us/training/wwl-azure/describe-core-architectural-components-of-azure/media/region-pairs-7c495a33.png}}
-== Azure management infrastructure ==
-{{https://learn.microsoft.com/en-us/training/modules/describe-core-architectural-components-of-azure/6-describe-azure-management-infrastructure}}
-== Azure resources and resource groups ==
-  * Resource groups are simply **groupings of resources**.
-  * When you create a resource, you’re **required to place it into a resource group**.
-  * There aren’t hard rules about how you use resource groups, so consider how to set up your resource groups to maximize their usefulness for you
-{{https://learn.microsoft.com/en-us/training/wwl-azure/describe-core-architectural-components-of-azure/media/resource-group-eb2d7177.png}}
-== Azure subscriptions ==
-  * **Billing boundary**: This subscription type determines how an Azure account is billed for using Azure. You can create multiple subscriptions for different types of billing requirements. Azure generates **separate billing reports** and invoices for each subscription so that you can organize and manage costs.
-  * **Access control boundary**: Azure applies access-management policies at the subscription level, and you can create separate subscriptions to reflect different organizational structures. An example is that within a business, you have **different departments** to which you apply distinct Azure subscription policies. This billing model allows you to manage and control access to the resources that users provision with specific subscriptions.
-{{https://learn.microsoft.com/en-us/training/wwl-azure/describe-core-architectural-components-of-azure/media/subscriptions-d415577b.png}}
-== Azure management groups ==
-  * You organize **subscriptions** into **containers called management groups** and apply governance conditions to the management groups.
-  * All subscriptions within a management group automatically i**nherit the conditions applied to the management group**,
-    * the same way that **resource groups inherit settings from subscriptions** and
-    * resources inherit from resource groups.
-{{https://learn.microsoft.com/en-us/training/wwl-azure/describe-core-architectural-components-of-azure/media/management-groups-subscriptions-dfd5a108.png}}
-  * E.g. You **could limit** VM locations to the **US West Region** in a group called **Production**.
-=== ESXi  ===
-Bare Metal Hypervisor
-https://www.parallels.com/blogs/ras/vmware-esxi/
-{{https://s3.eu-central-1.amazonaws.com/alf-digital-wiki-pics/sharex/9sxwipcsYv.png}}
-=== Virtual SAN (vSAN) ===
-VMware vSAN ist eine Storage-Virtualisierungssoftware für Unternehmen, die Hyper-Converged Infrastructure (HCI) unterstützt.
-VMware vSAN fasst lokale und direkt angeschlossene Datenspeichergeräte in einem VMware vSphere-Cluster zusammen, um einen einzigen Datenspeicher zu erstellen, den alle Hosts in einem vSAN-Cluster gemeinsam nutzen. VMware vSAN ist in den VMware-Hypervisor, ESXi, integriert.
-{{https://s3.eu-central-1.amazonaws.com/alf-digital-wiki-pics/sharex/D6HtMqS90L.png}}
-=== vSphere ===
-Der vCenter Server dient der Verwaltung einer vSphere-Infrastruktur. Er umfasst Funktionen zum Erzeugen, Löschen oder Ändern von virtuellen Data Centern