Study/AZ-104-MicrosoftAzureAdministrator
1
0
Fork 0
mirror of https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator.git synced 2026-02-05 08:09:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' into master

Browse Source
This commit is contained in:
polichtm 2020-07-16 05:16:34 -04:00 committed by GitHub
commit 12217e193e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
15 changed files with 69 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Allfiles/Labs/03/az104-03b-md-parameters.json
View File

@ -12,10 +12,13 @@
"value": "Standard_LRS"
},
"diskSizeGb": {
"value": "32"
"value": 32
},
"createOption": {
"value": "empty"
},
"diskEncryptionSetType": {
"value": "EncryptionAtRestWithPlatformKey"
}
}
}
}

7
Allfiles/Labs/03/az104-03b-md-template.json
View File

@ -12,7 +12,7 @@
"type": "String"
},
"diskSizeGb": {
"type": "String"
"type": "Int"
},
"sourceResourceId": {
"type": "String"
@ -29,6 +29,9 @@
"hyperVGeneration": {
"defaultValue": "V1",
"type": "String"
},
"diskEncryptionSetType": {
"type": "String"
}
},
"resources": [
@ -50,4 +53,4 @@
}
}
]
}
}

2
Instructions/Labs/LAB_01-Manage_Azure_AD_Identities.md
View File

@ -118,7 +118,7 @@ In this task, you will create Azure Active Directory groups with assigned and dy
| Group description | **Contoso IT cloud administrators** |
| Membership type | **Dynamic User** |
>**Note**: If the **Membership type** drop-down list is grayed out, refresh the browser page.
>**Note**: If the **Membership type** drop-down list is grayed out, wait a few minutes and refresh the browser page.
1. Click **Add dynamic query**.

2
Instructions/Labs/LAB_02a_Manage_Subscriptions_and_RBAC.md
View File

@ -41,6 +41,8 @@ In this task, you will create and configure management groups.
1. Search for and select **Management groups** and then, on the **Management groups** blade, click **+ Add management group**.
>**Note**: If you have not previously created Management Groups, select **Start using Management Groups**
1. Create a management group with the following settings:
| Setting | Value |

3
Instructions/Labs/LAB_03b-Manage_Azure_Resources_by_Using_ARM_Templates.md
View File

@ -48,7 +48,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource
#### Task 2: Create an Azure managed disk by using an ARM template
1. In the Azure portal, search for and select **Template deployment (deploy using custom templates)**.
1. In the Azure portal, search for and select **Template deployment (Deploy a custom template)**.
1. On the **Custom deployment** blade, click **Build your own template in the editor**.
@ -107,6 +107,7 @@ In this task, you will create an Azure disk resource by using an Azure Resource
| Sku | **Standard_LRS** |
| Disk Size Gb | **32** |
| Create Option | **empty** |
| Disk Encryption Set Type | **EncryptionAtRestWithPlatformKey** |
1. Select the checkbox **I agree to the terms and conditions stated above** and click **Purchase**.

2
Instructions/Labs/LAB_04-Implement_Virtual_Networking.md
View File

@ -42,7 +42,7 @@ In this task, you will create a virtual network with multiple subnets by using t
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you will be using in this lab |
| Resource Group | the name of a new resource group **az104-04-rg1** |
| Resource Group | the name of a **new** resource group **az104-04-rg1** |
| Name | **az104-04-vnet1** |
| Region | the name of any Azure region available in the subscription you will use in this lab |
| IPv4 address space | **10.40.0.0/20** |

6
Instructions/Labs/LAB_06-Implement_Network_Traffic_Management.md
View File

@ -126,7 +126,7 @@ In this task, you will configure local peering between the virtual networks you
| Name of the peering from az104-06-vnet2 to az104-06-vnet01 | **az104-06-vnet2_to_az104-06-vnet01** |
| Allow virtual network access from az104-06-vnet01 to az104-06-vnet2 | **Enabled** |
| Allow virtual network access from az104-06-vnet2 to az104-06-vnet01 | **Enabled** |
| Allow forwarded traffic from az104-06-vnet2 to az104-06-vnet01 | **Enabled** |
| Allow forwarded traffic from az104-06-vnet2 to az104-06-vnet01 | **Disabled** |
| Allow forwarded traffic from az104-06-vnet01 to az104-06-vnet2 | **Enabled** |
| Allow gateway transit | **(Uncheck Box)** |
@ -149,7 +149,7 @@ In this task, you will configure local peering between the virtual networks you
| Name of the peering from az104-06-vnet3 to az104-06-vnet01 | **az104-06-vnet3_to_az104-06-vnet01** |
| Allow virtual network access from az104-06-vnet01 to az104-06-vnet3 | **Enabled** |
| Allow virtual network access from az104-06-vnet3 to az104-06-vnet01 | **Enabled** |
| Allow forwarded traffic from az104-06-vnet3 to az104-06-vnet01 | **Enabled** |
| Allow forwarded traffic from az104-06-vnet3 to az104-06-vnet01 | **Disabled** |
| Allow forwarded traffic from az104-06-vnet01 to az104-06-vnet3 | **Enabled** |
| Allow gateway transit | **(Uncheck Box)** |
@ -524,7 +524,7 @@ In this task, you will implement an Azure Application Gateway in front of the tw
| Target type | **Backend pool** |
| Backend target | **az104-06-appgw5-be1** |
1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Create new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values):
1. On the **Backend targets** tab of the **Add a routing rule** blade, click **Add new** next to the **HTTP setting** text box, and, on the **Add an HTTP setting** blade, specify the following settings (leave others with their default values):
| Setting | Value |
| --- | --- |

10
Instructions/Labs/LAB_07-Manage_Azure_Storage.md
View File

@ -76,7 +76,7 @@ In this task, you will create and configure an Azure Storage account.
| Setting | Value |
| --- | --- |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | the name of a new resource group **az104-07-rg1** |
| Resource group | the name of a **new** resource group **az104-07-rg1** |
| Storage account name | any globally unique name between 3 and 24 in length consisting of letters and digits |
| Location | the name of an Azure region where you can create an Azure Storage account |
| Performance | **Standard** |
@ -168,7 +168,7 @@ In this task, you will configure authentication and authorization for Azure Stor
1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step.
1. You should be presented with an XML-formatted message stating **ResourceNotFound**.
1. You should be presented with an XML-formatted message stating **ResourceNotFound** or **PublicAccessNotPermitted**.
> **Note**: This is expected, since the container you created has the public access level set to **Private (no anonymous access)**.
@ -193,7 +193,7 @@ In this task, you will configure authentication and authorization for Azure Stor
1. Open another browser window by using InPrivate mode and navigate to the URL you copied in the previous step.
> **Note**: If you are using Microsoft Edge or Internet Explorer, you should be presented with the **The MIT License (MIT)** page. If you are using Chrome or Firefox, you should be able to view the content of the file by downloading it and opening it with Notepad.
> **Note**: If you are using Microsoft Edge or Internet Explorer, you should be presented with the **The MIT License (MIT)** page. If you are using Chrome, Microsoft Edge (Chromium) or Firefox, you should be able to view the content of the file by downloading it and opening it with Notepad.
> **Note**: This is expected, since now your access is authorized based on the newly generated the SAS token.
@ -207,7 +207,7 @@ In this task, you will configure authentication and authorization for Azure Stor
1. On the **az104-07-container** blade, click **Access Control (IAM)**.
1. In the **Add a role assignment** section, click **Add**.
1. In the **Add** section, click **Add a role assignment**.
1. On the **Add role assignment** blade, specify the following settings:
@ -219,6 +219,8 @@ In this task, you will configure authentication and authorization for Azure Stor
1. Save the change and return to the **Overview** blade of the **az104-07-container** container and verify that you can access to container again.
> **Note**: It might take about 5 minutes for the change to take effect.
#### Task 5: Create and configure an Azure Files shares
In this task, you will create and configure Azure Files shares.

5
Instructions/Labs/LAB_08-Manage_Virtual_Machines.md
View File

@ -265,6 +265,8 @@ In this task you will scale compute for Azure virtual machines by changing their
1. On the **Custom deployment** blade, click **Edit template**.
>**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case.
1. On the **Edit template** blade, in the section displaying the content of the template, replace the line **30** ` "vmSize": "Standard_D2s_v3"` with the following line):
```json
@ -274,7 +276,6 @@ In this task you will scale compute for Azure virtual machines by changing their
>**Note**: This section of the template defines the same Azure virtual machine size as the one you specified for the first virtual machine via the Azure portal.
1. On the **Edit template** blade, in the section displaying the content of the template, replace line **49** (` "dataDisks": [ ]` line) with the following code :
```json
@ -303,8 +304,6 @@ In this task you will scale compute for Azure virtual machines by changing their
1. Click **Save** and, back on the **Custom template** blade, enable the checkbox **I agree to the terms and conditions stated above** and click **Purchase**.
>**Note**: Disregard the message stating **The resource group is in a location that is not supported by one or more resources in the template. Please choose a different resource group**. This is expected and can be ignored in this case.
>**Note**: Wait for the template deployment to complete. You can monitor its progress from the **Extensions** blade of the **az104-08-vm1** virtual machine. This should take no more than 3 minutes.
1. Back on the **az104-08-vm1** blade, in the **Operations** section, click **Run command**, and, in the list of commands, click **RunPowerShellScript**.

8
Instructions/Labs/LAB_09a-Implement_Web_Apps.md
View File

@ -104,8 +104,10 @@ In this task, you will configure web app deployment settings.
| Setting | Value |
| --- | ---|
| User name | any unique name |
| Password | **P@55w0rd1234** |
| User name | any unique name (must not contain `@` character) |
| Password | any password that satisfies complexity requirements |
>**Note:** The password must be at least eight characters long, with two of the following three elements: letters, numbers, and non-alphanumeric characters.
>**Note:** You will need these credentials in the next task of this lab.
@ -144,7 +146,7 @@ In this task, you will deploy code to the staging deployment slot.
git push [deployment_user_name] master
```
1. If prompted to authenticate, type the `[deployment_user_name]` and the corresponding password (**P@55w0rd1234**).
1. If prompted to authenticate, type the `[deployment_user_name]` and the corresponding password (which you set in the previous task).
1. Close the Cloud Shell pane.

6
Instructions/Labs/LAB_09c-Implement_Azure_Kubernetes_Service.md
View File

@ -64,10 +64,10 @@ In this task, you will deploy an Azure Kubernetes Services cluster by using the
| Setting | Value |
| ---- | ---- |
| DNS name prefix | any valid, globally unique DNS host name |
| HTTP application routing | **No** |
| Load balancer | **Standard** |
| Network configuration | **Advanced** |
| DNS name prefix | any valid, globally unique DNS host name |
| Load balancer | **Standard** |
| HTTP application routing | **No** |
1. Click **Next: Integration >**, on the **Integration** tab of the **Create Kubernetes cluster** blade, set **Container monitoring** to **Disabled**, click **Review + create** and then click **Create**.

4
Instructions/Labs/LAB_10-Implement_Data_Protection.md
View File

@ -120,7 +120,7 @@ In this task, you will implement Azure virtual-machine level backup.
1. On the **Backup Goal** blade, click **Backup**.
1. On the **Backup policy**, review the **DefaultPolicy** settings, and, in the **Choose backup policy** drop-down list, select **Create New**.
1. On the **Backup policy**, review the **DefaultPolicy** settings and select **Create a new policy**.
1. Define a new backup policy with the following settings (leave others with their default values):
@ -132,7 +132,7 @@ In this task, you will implement Azure virtual-machine level backup.
| Timezone | the name of your local time zone |
| Retain instant recovery snapshot(s) for | **2** Days(s) |
1. Click **OK** to create the policy. This will automatically transition to the **Items to backup** step and open the **Select virtual machines** blade.
1. Click **OK** to create the policy and then, in the **Virtual Machines** section, select **Add**.
1. On the **Select virtual machines** blade, select **az-104-10-vm0**, click **OK**, and, back on the **Backup** blade, click **Enable backup**.

47
Instructions/Labs/LAB_11-Implement_Monitoring.md
View File

@ -84,15 +84,14 @@ In this task, you will create and configure an Azure Log Analytics workspace and
1. In the Azure portal, search for and select **Log Analytics workspaces** and, on the **Log Analytics workspaces** blade, click **+ Add**.
1. On the **Log Analytics workspace** blade, ensure that the **Create New** option is selected, specify the following settings, and click **OK**:
1. On the **Basics** tab of the **Create Log Analytics workspace** blade, the following settings, click **Review + Create** and then click **Create**:
| Settings | Value |
| --- | --- |
| Log Analytics Workspace | any unique name |
| Subscription | the name of the Azure subscription you are using in this lab |
| Resource group | the name of a new resource group **az104-11-rg1** |
| Location | the name of the Azure region into which you deployed the virtual machine in the previous task |
| Pricing tier | **Pay-as-you-go** |
| Log Analytics Workspace | any unique name |
| Region | the name of the Azure region into which you deployed the virtual machine in the previous task |
>**Note**: Make sure that you specify the same region into which you deployed virtual machines in the previous task.
@ -136,15 +135,15 @@ In this task, you will review default monitoring settings of Azure virtual machi
1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Metrics**.
1. On the **az104-11-vm0 - Metrics** blade, on the default chart, note that the only available **METRICS NAMESPACE** is **Virtual Machine Host**.
1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that the only available **Metrics Namespace** is **Virtual Machine Host**.
>**Note**: This is expected, since no guest-level diagnostic settings have been configured yet.
1. In the **METRICS** drop-down list, review the list of available metrics.
1. In the **Metric** drop-down list, review the list of available metrics.
>**Note**: The list includes a range of CPU, disk, and network-related metrics that can be collected from the virtual machine host, without having access into guest-level metrics.
1. In the **METRICS** drop-down list, select **Percentage CPU**, in the **AGGREGATION** drop-down list, select **Avg**, and review the resulting chart.
1. In the **Metric** drop-down list, select **Percentage CPU**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart.
#### Task 5: Configure Azure virtual machine diagnostic settings
@ -152,15 +151,15 @@ In this task, you will configure Azure virtual machine diagnostic settings.
1. On the **az104-11-vm0** blade, in the **Monitoring** section, click **Diagnostic settings**.
1. On the **Overview** tab of the **az104-11-vm0 - Diagnostic settings** blade, click **Enable guest-level monitoring**.
1. On the **Overview** tab of the **az104-11-vm0 | Diagnostic settings** blade, click **Enable guest-level monitoring**.
>**Note**: Wait for the operation to take effect. This might take about 3 minutes.
1. Switch to the **Performance counters** tab of the **az104-11-vm0 - Diagnostic settings** blade and review the available counters.
1. Switch to the **Performance counters** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available counters.
>**Note**: By default, CPU, memory, disk, and network counters are enabled. You can switch to the **Custom** view for more detailed listing.
1. Switch to the **Logs** tab of the **az104-11-vm0 - Diagnostic settings** blade and review the available event log collection options.
1. Switch to the **Logs** tab of the **az104-11-vm0 | Diagnostic settings** blade and review the available event log collection options.
>**Note**: By default, log collection includes critical, error, and warning entries from the Application Log and System log, as well as Audit failure entries from the Security log. Here as well you can switch to the **Custom** view for more detailed configuration settings.
@ -170,23 +169,21 @@ In this task, you will configure Azure virtual machine diagnostic settings.
>**Note**: Do not wait for the operation to complete but instead proceed to the next step. The operation might take about 5 minutes.
1. On the **az104-11-vm0 - Logs** blade, in the **Monitoring** section, click **Metrics**.
1. On the **az104-11-vm0 | Logs** blade, in the **Monitoring** section, click **Metrics**.
1. On the **az104-11-vm0 - Metrics** blade, on the default chart, note that at this point, the **METRICS NAMESPACE** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry.
1. On the **az104-11-vm0 | Metrics** blade, on the default chart, note that at this point, the **Metrics Namespace** drop-down list, in addition to the **Virtual Machine Host** entry includes also the **Guest (classic)** entry.
>**Note**: This is expected, since you enabled guest-level diagnostic settings.
1. In the **METRICS** drop-down list, review the list of available metrics.
1. In the **Metric** drop-down list, review the list of available metrics.
>**Note**: The list includes additional guest-level metrics not available when relying on the host-level monitoring only.
1. In the **METRICS** drop-down list, select **Memory\Available Bytes**, in the **AGGREGATION** drop-down list, select **Avg**, and review the resulting chart.
1. In the **Metric** drop-down list, select **Memory\Available Bytes**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart.
#### Task 6: Review Azure Monitor functionality
1. In the Azure portal, search for and select **Monitor** and, on the **Monitor - Overview** blade, click **Metrics**.
1. In the chart pane on the right side of the blade, in the **SCOPE** drop-down list, click **+ Select a scope**.
1. In the Azure portal, search for and select **Monitor** and, on the **Monitor | Overview** blade, click **Metrics**.
1. On the **Select a scope** blade, on the **Browse** tab, navigate to the **az104-11-rg0** resource group, expand it, select the **az104-11-vm0** virtual machine within that resource group, and click **Apply**.
@ -194,11 +191,11 @@ In this task, you will configure Azure virtual machine diagnostic settings.
1. In the **Metric** drop-down list, select **Percentage CPU**, in the **Aggregation** drop-down list, select **Avg**, and review the resulting chart.
1. On the **Monitor - Metrics** blade, click **New alert rule**.
1. On the **Monitor | Metrics** blade, click **New alert rule**.
>**Note**: Creating an alert rule from Metrics is not supported for metrics from the Guest (classic) metric namespace. This can be accomplished by using Azure Resource Manager templates, as described in the document [Send Guest OS metrics to the Azure Monitor metric store using a Resource Manager template for a Windows virtual machine](https://docs.microsoft.com/en-us/azure/azure-monitor/platform/collect-custom-metrics-guestos-resource-manager-vm)
1. On the **Create alert rule** blade, in the **CONDITION** section, click the existing condition.
1. On the **Create alert rule** blade, in the **Condition** section, click the existing condition.
1. On the **Configure signal logic** blade, in the list of signals, in the **Alert logic** section, specify the following settings (leave others with their default values) and click **Done**:
@ -284,7 +281,17 @@ In this task, you will configure Azure virtual machine diagnostic settings.
1. On the **Select a scope** blade, navigate to the **az104-11-rg0** resource group, expand it, select **a104-11-vm0**, and click **Apply**.
1. Click **Example queries** in the toolbar, in the **Get started with sample queries** pane, review each tab, locate **Virtual machine available memory**, and click **Run**.
1. In the query window, paste the following query and click **Run**:
```
// Virtual Machine available memory
// Chart the VM's available memory over the last hour.
InsightsMetrics
| where TimeGenerated > ago(1h)
| where Name == "AvailableMB"
| project TimeGenerated, Name, Val
| render timechart
```
1. Click **Example queries** in the toolbar, in the **Get started with sample queries** pane, review each tab, locate **Track VM availability**, and click **Run**.

2
_config.yml
View File

@ -15,3 +15,5 @@ markdown: kramdown
kramdown:
syntax_highlighter_opts:
disable : true
theme: jekyll-theme-slate

4
index.md
View File

@ -6,7 +6,9 @@ layout: home
# Content Directory
Hyperlinks to each of the lab exercises and demos are listed below.
Required labs files can be [DOWNLOADED HERE](https://github.com/MicrosoftLearning/AZ-104-MicrosoftAzureAdministrator/archive/master.zip)
Hyperlinks to each of the lab exercises are listed below.
## Labs