certification:azure-foundational
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
certification:azure-foundational [2024/02/20 21:07] – skipidar | certification:azure-foundational [2024/09/05 19:48] (current) – skipidar | ||
---|---|---|---|
Line 4: | Line 4: | ||
https:// | https:// | ||
+ | |||
+ | Exam AZ-303: Microsoft Azure Architect | ||
+ | https:// | ||
Azure for AWS | Azure for AWS | ||
Line 10: | Line 13: | ||
* https:// | * https:// | ||
- | Submodules | + | Submodules: |
- | * https:// | ||
- | * https:// | ||
+ | ✔️ Microsoft Azure Fundamentals: | ||
+ | https:// | ||
- | === Security Group === | ||
- | Unlike the AWS security group which is always associated with an instance, | + | Microsoft |
+ | https:// | ||
- | | + | |
- | * NSG can be associated with the VM (Classic) | + | * ✔️ Describe the core architectural components of Azure https:// |
- | * NSG can be associated with the network interfaces (NIC) attached to VMs (Resource Manager) | + | * ✔️ Describe Azure compute and networking services https:// |
+ | * ✔️ Describe Azure storage services https:// | ||
+ | * Describe Azure identity, access, and security https:// | ||
+ | |||
+ | |||
+ | Microsoft Azure Fundamentals: | ||
+ | https:// | ||
+ | |||
+ | * Describe cost management in Azure https:// | ||
+ | * Describe features and tools in Azure for governance and compliance https:// | ||
+ | * Describe features and tools for managing and deploying Azure resources https:// | ||
+ | * Describe monitoring tools in Azure https:// | ||
+ | |||
+ | |||
+ | === Network Security Group NSG === | ||
+ | |||
+ | Unlike the AWS security group which is always associated with an instance, Azure Network Security Group (NSG) can be associated with three different entities: | ||
+ | |||
+ | | ||
+ | * NSG can be associated with **the VM (Classic)** | ||
+ | * NSG can be associated with the **network interfaces** (NIC) attached to VMs (Resource Manager) | ||
AWS vs Azure Security Groups | AWS vs Azure Security Groups | ||
Line 29: | Line 52: | ||
- | === Network === | ||
- | |||
- | * https:// | ||
- | * Default outbound access in Azure | ||
- | | ||
=== Spec === | === Spec === | ||
Line 77: | Line 95: | ||
==== Knowhow ==== | ==== Knowhow ==== | ||
- | |||
- | === Azure physical infrastructure === | ||
- | |||
- | https:// | ||
- | |||
- | == Availability Zones == | ||
- | |||
- | {{https:// | ||
- | |||
- | |||
- | == 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:// | ||
- | |||
- | |||
- | == Azure management infrastructure == | ||
- | |||
- | {{https:// | ||
- | |||
- | == 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:// | ||
- | |||
- | |||
- | == 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:// | ||
- | |||
- | |||
- | == 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:// | ||
- | |||
- | * E.g. You **could limit** VM locations to the **US West Region** in a group called **Production**. | ||
- | |||
- | |||
- | === ESXi === | ||
- | |||
- | Bare Metal Hypervisor | ||
- | |||
- | https:// | ||
- | |||
- | {{https:// | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | === Virtual SAN (vSAN) === | ||
- | |||
- | VMware vSAN ist eine Storage-Virtualisierungssoftware für Unternehmen, | ||
- | |||
- | 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, | ||
- | |||
- | {{https:// | ||
- | |||
- | |||
- | === vSphere === | ||
- | |||
- | Der vCenter Server dient der Verwaltung einer vSphere-Infrastruktur. Er umfasst Funktionen zum Erzeugen, Löschen oder Ändern von virtuellen Data Centern | ||
- | |||
certification/azure-foundational.1708463273.txt.gz · Last modified: by skipidar