matze/docs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[logseq-plugin-git:commit] 2025-07-16T14:43:18.052Z

Browse Source
This commit is contained in:
Matthias Eckert 2025-07-16 16:43:18 +02:00
parent e17f2815f0
commit 42c21f05d7
1 changed files with 68 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
pages/Learning ___ Azure ___ AZ-900%3A Microsoft Azure Fundamentals.md
View File

@ -145,7 +145,7 @@
- 10,000 management groups can be supported in a single directory. - 10,000 management groups can be supported in a single directory.
- A management group tree can support up to six levels of depth. This limit doesn't include the root level or the subscription level. - A management group tree can support up to six levels of depth. This limit doesn't include the root level or the subscription level.
- Each management group and subscription can support only one parent. - Each management group and subscription can support only one parent.
- ## Describe Azure compute and networking services - ## Azure compute and networking services
- Goals - Goals
- Compare compute types, including container instances, virtual machines, and functions - Compare compute types, including container instances, virtual machines, and functions
- Describe virtual machine (VM) options, including VMs, Virtual Machine Scale Sets, availability sets, Azure Virtual Desktop - Describe virtual machine (VM) options, including VMs, Virtual Machine Scale Sets, availability sets, Azure Virtual Desktop
@ -279,4 +279,70 @@
- manage your domains and records with the Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI. - manage your domains and records with the Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI.
- #### Customizable virtual networks with private domains - #### Customizable virtual networks with private domains
- #### Alias records - #### Alias records
- ## Azure storage services
- Goals
- Compare Azure storage services.
- Describe storage tiers.
- Describe redundancy options.
- Describe storage account options and storage types.
- Identify options for moving files, including AzCopy, Azure Storage Explorer, and Azure File Sync.
- Describe migration options, including Azure Migrate and Azure Data Box.
- ### Azure storage accounts
- Locally redundant storage (LRS)
- Zone-redundant storage (ZRS)
- Geo-redundant storage (GRS)
- Geo-zone-redundant storage (GZRS)
- Read-access geo-redundant storage (RA-GRS)
- Read-access geo-zone-redundant storage (RA-GZRS)
- | **Type** | **Supported services** | **Redundancy Options** | **Usage** |
| ---- | ---- | ---- |
| Standard general-purpose v2 | Blob Storage (including Data Lake Storage), Queue Storage, Table Storage, and Azure Files | LRS, GRS, RA-GRS, ZRS, GZRS, RA-GZRS | Standard storage account type for blobs, file shares, queues, and tables. Recommended for most scenarios using Azure Storage. If you want support for network file system (NFS) in Azure Files, use the premium file shares account type. |
| Premium block blobs | Blob Storage (including Data Lake Storage) | LRS, ZRS | Premium storage account type for block blobs and append blobs. Recommended for scenarios with high transaction rates or that use smaller objects or require consistently low storage latency. |
| Premium file shares | Azure Files | LRS, ZRS | Premium storage account type for file shares only. Recommended for enterprise or high-performance scale applications. Use this account type if you want a storage account that supports both Server Message Block (SMB) and NFS file shares. |
| Premium page blobs | Page blobs only | LRS | Premium storage account type for page blobs only |
- #### Storage account endpoints
- between 3 and 24 characters in length and may contain numbers and lowercase letters only.
- unique within Azure
- | **Storage service** | **Endpoint** |
| ---- | ---- | ---- |
| Blob Storage | https://<storage-account-name>.blob.core.windows.net |
| Data Lake Storage Gen2 | https://<storage-account-name>.dfs.core.windows.net |
| Azure Files | https://<storage-account-name>.file.core.windows.net |
| Queue Storage | https://<storage-account-name>.queue.core.windows.net |
| Table Storage | https://<storage-account-name>.table.core.windows.net |
- ### Azure storage redundancy
- #### Redundancy in the primary region
- **Locally redundant storage**
- ![Diagram showing the structure used for locally redundant storage.](https://learn.microsoft.com/en-us/training/wwl-azure/describe-azure-storage-services/media/locally-redundant-storage.png)
- **Zone-redundant storage**
- ![Diagram showing ZRS, with a copy of data stored in each of three availability zones.](https://learn.microsoft.com/en-us/training/wwl-azure/describe-azure-storage-services/media/zone-redundant-storage.png)
- #### Redundancy in a secondary region
- **Geo-redundant storage**
- ![Diagram showing GRS, with primary region LRS replicating data to LRS in a second region.](https://learn.microsoft.com/en-us/training/wwl-azure/describe-azure-storage-services/media/geo-redundant-storage.png)
- **Geo-zone-redundant storage**
- ![Diagram showing GZRS, with primary region ZRS replicating data to LRS in a second region.](https://learn.microsoft.com/en-us/training/wwl-azure/describe-azure-storage-services/media/geo-zone-redundant-storage.png)
- **Read access to data in the secondary region**
- GRS and GZRS with read access (normally not possible)
- ### Azure storage services
- **Azure Blobs**: A massively scalable object store for text and binary data. Also includes support for big data analytics through Data Lake Storage Gen2.
- **Hot access tier**: Optimized for storing data that is accessed frequently (for example, images for your website).
- **Cool access tier**: Optimized for data that is infrequently accessed and stored for at least 30 days (for example, invoices for your customers).
- **Cold access tier**: Optimized for storing data that is infrequently accessed and stored for at least 90 days.
- **Archive access tier**: Appropriate for data that is rarely accessed and stored for at least 180 days, with flexible latency requirements (for example, long-term backups).
- **Azure Files**: Managed file shares for cloud or on-premises deployments.
- accessible Server Message Block (SMB) or Network File System (NFS) protocols
- **Azure Queues**: A messaging store for reliable messaging between application components.
- **Azure Disks**: Block-level storage volumes for Azure VMs.
- **Azure Tables:** NoSQL table option for structured, non-relational data.
- ### Identify Azure data migration options
- **Azure Migrate: Discovery and assessment**. Discover and assess on-premises servers running on VMware, Hyper-V, and physical servers in preparation for migration to Azure.
- **Azure Migrate: Server Migration**. Migrate VMware VMs, Hyper-V VMs, physical servers, other virtualized servers, and public cloud VMs to Azure.
- **Data Migration Assistant**. Data Migration Assistant is a stand-alone tool to assess SQL Servers. It helps pinpoint potential problems blocking migration. It identifies unsupported features, new features that can benefit you after migration, and the right path for database migration.
- **Azure Database Migration Service**. Migrate on-premises databases to Azure VMs running SQL Server, Azure SQL Database, or SQL Managed Instances.
- **Azure App Service migration assistant**. Azure App Service migration assistant is a standalone tool to assess on-premises websites for migration to Azure App Service. Use Migration Assistant to migrate .NET and PHP web apps to Azure.
- **Azure Data Box**. Use Azure Data Box products to move large amounts of offline data to Azure. Suited to transfer data sizes larger than 40 TBs - 80 TB
- ### Azure file movement options
- **AzCopy** copy blobs or files to or from your storage account
- **Azure Storage Explorer** standalone app
- **Azure File Sync** stay bi-directionally synced with your files in Azure.
- -