Take this free AZ-104 mock test designed for 2026 exam prep. Simulate the Microsoft Azure Administrator certification experience with real-world questions and answers. Perfect for last-minute revision or full practice sessions.
Report a question
Welcome ! Try to score 80 %. Good Luck.
AZ-104 Practice Set 7
Prepare for the AZ-104 certification exam with our comprehensive practice set, featuring a range of questions designed to test your knowledge of Microsoft Azure administration. This practice set includes one detailed case study question that reflects the real-world scenarios you’ll encounter on the exam.
Our practice questions cover all key topics, including managing Azure identities and governance, implementing and managing storage, deploying and managing Azure compute resources, configuring and managing virtual networking, and monitoring and backing up Azure resources.
Each question comes with thorough explanations to help you understand the concepts and prepare effectively for the exam. The case study question is designed to enhance your problem-solving skills and give you a taste of what to expect in the actual test.
Get started today with our AZ-104 practice set and take the next step toward becoming a certified Azure Administrator!
Note: To Zoom the Picture click/touch it
1 / 42
1. Scenario:
Your company has several Azure Virtual Machines (VMs) running different workloads in various regions. You need to implement a centralized log aggregation and analysis solution to monitor these VMs. You‘re considering Azure Monitor and Log Analytics workspace to collect and store logs from the VMs.
You‘ve gathered the following information about your VMs:
Question:
Given the scenario and VM details, which of the following configurations would be the MOST efficient and cost-effective for collecting and storing diagnostic logs for all your VMs using Azure Monitor and Log Analytics workspaces?
Here‘s why:
Regional Affinity: Creating a Log Analytics workspace in each region where your VMs are located minimizes latency and data transfer costs. Azure Monitor is designed to work optimally when logs are collected and stored in the same region as the resources generating them.
Cost Efficiency: By keeping logs within their respective regions, you avoid unnecessary data transfer charges between regions.
Why other options are not as suitable:
Sending all logs to a single workspace in East US would result in higher latency and potentially higher costs for data transfer from other regions.
While using a central region might seem convenient, it would still incur data transfer costs from VMs in other regions.
Creating a Log Analytics workspace for each resource group could lead to unnecessary complexity and increased management overhead, especially if multiple VMs share the same resource group.
Key Points:
This scenario emphasizes the importance of understanding the cost and performance implications of log aggregation in a multi-region Azure environment.
Azure Monitor and Log Analytics workspaces are powerful tools for centralized logging and analysis, but proper configuration is essential for optimal performance and cost-effectiveness.
Here‘s why:
Regional Affinity: Creating a Log Analytics workspace in each region where your VMs are located minimizes latency and data transfer costs. Azure Monitor is designed to work optimally when logs are collected and stored in the same region as the resources generating them.
Cost Efficiency: By keeping logs within their respective regions, you avoid unnecessary data transfer charges between regions.
Why other options are not as suitable:
Sending all logs to a single workspace in East US would result in higher latency and potentially higher costs for data transfer from other regions.
While using a central region might seem convenient, it would still incur data transfer costs from VMs in other regions.
Creating a Log Analytics workspace for each resource group could lead to unnecessary complexity and increased management overhead, especially if multiple VMs share the same resource group.
Key Points:
This scenario emphasizes the importance of understanding the cost and performance implications of log aggregation in a multi-region Azure environment.
Azure Monitor and Log Analytics workspaces are powerful tools for centralized logging and analysis, but proper configuration is essential for optimal performance and cost-effectiveness.
2 / 42
2. Scenario:
Your company, a financial institution, stores large volumes of sensitive customer data in Azure Blob Storage. To optimize costs and comply with data retention policies, you need to automate the lifecycle management of this data. Specifically, you need to:
Transition older data to cooler storage tiers based on last accessed time.
Permanently delete sensitive customer data after a specified retention period.
Preserve the ability to recover accidentally deleted data for a limited time.
Question:
Which Azure features or tools should you use to implement this automated data lifecycle management process?
More details:
Azure Blob Storage lifecycle management policies: These policies allow you to create rules to automatically transition blobs to cooler storage tiers (Cool, Archive) based on criteria like last accessed time. You can also define rules to permanently delete blobs after a specified period, aligning with your data retention policies.
Azure Blob soft delete: This feature enables you to recover blobs that have been accidentally deleted within a retention period you configure. It provides a safety net for data recovery in case of unintended deletions.
Azure Monitor: Azure Monitor allows you to track and analyze the effectiveness of your lifecycle management policies. You can create alerts to notify you of any issues or unexpected behavior, ensuring your policies are working as intended.
Why other options are not suitable:
While Azure Blob Inventory provides insights into storage usage, it doesn‘t automate lifecycle management. Azure Event Grid can trigger actions, but it needs to be coupled with other tools to define the lifecycle rules. Azure Data Factory is used for orchestrating data movement and transformation, but it‘s not the primary tool for lifecycle management within Azure Storage.
Access tiers are part of the lifecycle management strategy, but they need to be combined with lifecycle management policies to be automated. Versioning is useful for maintaining historical versions of blobs, but it doesn‘t directly address automatic deletion or transition to cooler tiers.
These tools focus on data security and compliance, not on the automated movement or deletion of data based on lifecycle criteria.
More details:
Azure Blob Storage lifecycle management policies: These policies allow you to create rules to automatically transition blobs to cooler storage tiers (Cool, Archive) based on criteria like last accessed time. You can also define rules to permanently delete blobs after a specified period, aligning with your data retention policies.
Azure Blob soft delete: This feature enables you to recover blobs that have been accidentally deleted within a retention period you configure. It provides a safety net for data recovery in case of unintended deletions.
Azure Monitor: Azure Monitor allows you to track and analyze the effectiveness of your lifecycle management policies. You can create alerts to notify you of any issues or unexpected behavior, ensuring your policies are working as intended.
Why other options are not suitable:
While Azure Blob Inventory provides insights into storage usage, it doesn‘t automate lifecycle management. Azure Event Grid can trigger actions, but it needs to be coupled with other tools to define the lifecycle rules. Azure Data Factory is used for orchestrating data movement and transformation, but it‘s not the primary tool for lifecycle management within Azure Storage.
Access tiers are part of the lifecycle management strategy, but they need to be combined with lifecycle management policies to be automated. Versioning is useful for maintaining historical versions of blobs, but it doesn‘t directly address automatic deletion or transition to cooler tiers.
These tools focus on data security and compliance, not on the automated movement or deletion of data based on lifecycle criteria.
3 / 42
3. Scenario:
Your company has been rapidly expanding its cloud footprint on Azure, deploying numerous resources across multiple subscriptions. As a result, you‘re experiencing increasing challenges in understanding, managing, and optimizing your Azure costs.
Specifically, you‘re facing the following issues:
1. Unexpected cost spikes: You‘ve noticed sudden increases in your monthly Azure bill that you can‘t readily explain.
2. Resource Overprovisioning: You suspect that some of your resources are overprovisioned and not being utilized efficiently.
3. Lack of Cost Visibility: You need a way to break down your Azure costs by resource type, subscription, and department to better understand your spending patterns.
4. Budget Overruns: You need to establish budgets for different departments and projects to prevent unexpected cost overruns.
Question:
Which combination of Azure Cost Management and Billing features would BEST address these challenges and help you gain better control over your Azure spending?
The best answer is Cost analysis, Azure Advisor recommendations, and Azure budgets. Here‘s why:
Cost analysis: This feature provides a detailed breakdown of your Azure costs, allowing you to identify cost drivers, analyze spending trends, and compare costs across different time periods, subscriptions, and resource groups. This addresses the lack of cost visibility.
Azure Advisor recommendations: This tool analyzes your resource usage and provides personalized recommendations for optimizing costs, such as rightsizing VMs, deleting unused resources, or purchasing reserved instances. This addresses resource overprovisioning and helps prevent unexpected cost spikes.
Azure budgets: This feature enables you to set spending limits for your Azure resources and receive alerts when you approach or exceed those limits. This helps you stay on top of your spending and prevent budget overruns.
Why other options are less ideal:
While Azure reservations can help reduce costs, they are not the most effective solution for analyzing spending patterns or identifying overprovisioned resources.
Azure Cost Management APIs can be useful for automating cost management tasks, but they are not the primary tools for cost analysis or budget setting.
This combination focuses more on cost reporting and optimization but lacks the proactive alerting and budget control features of Azure budgets.
Key Points:
This scenario highlights the challenges that organizations face in managing cloud costs as their Azure footprint grows.
It emphasizes the importance of utilizing the various features offered by Azure Cost Management and Billing to gain insights into spending patterns, optimize resource utilization, and prevent unexpected costs.
The best answer is Cost analysis, Azure Advisor recommendations, and Azure budgets. Here‘s why:
Cost analysis: This feature provides a detailed breakdown of your Azure costs, allowing you to identify cost drivers, analyze spending trends, and compare costs across different time periods, subscriptions, and resource groups. This addresses the lack of cost visibility.
Azure Advisor recommendations: This tool analyzes your resource usage and provides personalized recommendations for optimizing costs, such as rightsizing VMs, deleting unused resources, or purchasing reserved instances. This addresses resource overprovisioning and helps prevent unexpected cost spikes.
Azure budgets: This feature enables you to set spending limits for your Azure resources and receive alerts when you approach or exceed those limits. This helps you stay on top of your spending and prevent budget overruns.
Why other options are less ideal:
While Azure reservations can help reduce costs, they are not the most effective solution for analyzing spending patterns or identifying overprovisioned resources.
Azure Cost Management APIs can be useful for automating cost management tasks, but they are not the primary tools for cost analysis or budget setting.
This combination focuses more on cost reporting and optimization but lacks the proactive alerting and budget control features of Azure budgets.
Key Points:
This scenario highlights the challenges that organizations face in managing cloud costs as their Azure footprint grows.
It emphasizes the importance of utilizing the various features offered by Azure Cost Management and Billing to gain insights into spending patterns, optimize resource utilization, and prevent unexpected costs.
4 / 42
4. Your company is modernizing its application development process by adopting containerization. You are tasked with designing a containerized solution in Azure that meets the following requirements:
Scalability: The application needs to scale dynamically to handle varying workloads.
Portability: The containers should be able to run seamlessly across different environments (development, testing, and production).
Security: The container environment should be isolated and protected from potential threats.
Monitoring: You need to track the health and performance of the containers in real time.
Deployment Automation: You need a way to automate the deployment and management of containerized applications.
The company has an existing Azure Kubernetes Service (AKS) cluster and is considering Azure Container Instances (ACI) for running ephemeral tasks.
Question:
Given the scenario and requirements, which of the following solutions would BEST address the company‘s needs?
The mentioned is the best answer, Here‘s why:
Hybrid Approach: This solution leverages the strengths of both AKS and ACI. Long-running services that require persistent storage and complex orchestration are deployed in AKS, while short-lived tasks that are stateless and don‘t require high availability can be run in ACI. This approach provides the flexibility to choose the right tool for the job.
Scalability: AKS provides built-in mechanisms for scaling pods based on demand, while ACI automatically scales based on the task requirements.
Portability: Container images stored in ACR can be easily deployed to either AKS or ACI, ensuring consistency across environments.
Security: AKS provides network isolation and role-based access control (RBAC), while ACI isolates containers by default.
Monitoring: Azure Monitor integrates seamlessly with both AKS and ACI, providing comprehensive monitoring and logging capabilities.
Deployment Automation: Azure Pipelines enables CI/CD pipelines for automated building, testing, and deployment of container images to both AKS and ACI.
Why other options are less ideal:
While AKS is a powerful orchestrator, it may not be the most cost-effective solution for running short-lived tasks.
ACI is ideal for serverless tasks, but it lacks the features needed for complex orchestration and persistent storage required by long-running services.
A hybrid environment introduces additional complexity and may not be necessary for all organizations.
Key Points:
This question tests your understanding of containerization concepts and the different Azure services available for running containerized applications.
It assesses your ability to design a complex solution that balances scalability, portability, security, monitoring, and deployment automation.
It challenges you to choose the right combination of services to meet the specific requirements of the scenario.
The mentioned is the best answer, Here‘s why:
Hybrid Approach: This solution leverages the strengths of both AKS and ACI. Long-running services that require persistent storage and complex orchestration are deployed in AKS, while short-lived tasks that are stateless and don‘t require high availability can be run in ACI. This approach provides the flexibility to choose the right tool for the job.
Scalability: AKS provides built-in mechanisms for scaling pods based on demand, while ACI automatically scales based on the task requirements.
Portability: Container images stored in ACR can be easily deployed to either AKS or ACI, ensuring consistency across environments.
Security: AKS provides network isolation and role-based access control (RBAC), while ACI isolates containers by default.
Monitoring: Azure Monitor integrates seamlessly with both AKS and ACI, providing comprehensive monitoring and logging capabilities.
Deployment Automation: Azure Pipelines enables CI/CD pipelines for automated building, testing, and deployment of container images to both AKS and ACI.
Why other options are less ideal:
While AKS is a powerful orchestrator, it may not be the most cost-effective solution for running short-lived tasks.
ACI is ideal for serverless tasks, but it lacks the features needed for complex orchestration and persistent storage required by long-running services.
A hybrid environment introduces additional complexity and may not be necessary for all organizations.
Key Points:
This question tests your understanding of containerization concepts and the different Azure services available for running containerized applications.
It assesses your ability to design a complex solution that balances scalability, portability, security, monitoring, and deployment automation.
It challenges you to choose the right combination of services to meet the specific requirements of the scenario.
5 / 42
5. Scenario: Your company has a complex Azure environment with multiple virtual networks (VNets) in different regions. You have several critical applications hosted on VMs in these VNets. The applications need to communicate securely with each other, and you also need to provide access to these applications for on-premises users through a site-to-site VPN connection. However, you are facing the following challenges:
Limited Public IP Addresses: You have a limited number of public IP addresses available.
Security Concerns: You need to ensure that communication between the applications and from on-premises is secure.
Cost Optimization: You need to minimize the cost of network traffic between the VNets.
Task:
Which combination of Azure services would BEST address these challenges?
The Azure Virtual WAN, Azure Firewall, and Azure VPN Gateway. Here‘s why:
Azure Virtual WAN: This service simplifies the creation of a large-scale, global WAN architecture in Azure. It allows you to connect multiple VNets and on-premises sites using various connection options, including site-to-site VPN and ExpressRoute.
Azure Firewall: This cloud-native firewall service provides centralized network security for your Azure resources. It allows you to filter traffic based on fully qualified domain names (FQDNs), IP addresses, ports, and protocols, ensuring secure communication between VNets.
Azure VPN Gateway: This service enables secure, encrypted communication between Azure VNets and on-premises networks over the public internet. It can be integrated with Azure Virtual WAN to create a unified network architecture.
This combination addresses all of the challenges:
Limited Public IPs: Virtual WAN allows you to connect VNets using private IP addresses, reducing the need for public IPs.
Security: Azure Firewall provides robust network security, filtering traffic and protecting against threats.
Cost Optimization: Virtual WAN optimizes traffic routing between VNets, minimizing costs.
Why other options are less suitable:
Azure Bastion is used for secure management of VMs, but it doesn‘t address the other challenges.
Azure ExpressRoute is a dedicated private connection to Azure, but it may not be the most cost-effective option for smaller organizations.
Azure Load Balancer is used for load balancing traffic, but it doesn‘t provide the same level of network security as Azure Firewall.
Key Points:
This question tests your understanding of complex Azure networking scenarios.
It assesses your ability to choose the right combination of services to address multiple challenges simultaneously.
This scenario requires knowledge of both virtual network connectivity and network security in Azure.
The Azure Virtual WAN, Azure Firewall, and Azure VPN Gateway. Here‘s why:
Azure Virtual WAN: This service simplifies the creation of a large-scale, global WAN architecture in Azure. It allows you to connect multiple VNets and on-premises sites using various connection options, including site-to-site VPN and ExpressRoute.
Azure Firewall: This cloud-native firewall service provides centralized network security for your Azure resources. It allows you to filter traffic based on fully qualified domain names (FQDNs), IP addresses, ports, and protocols, ensuring secure communication between VNets.
Azure VPN Gateway: This service enables secure, encrypted communication between Azure VNets and on-premises networks over the public internet. It can be integrated with Azure Virtual WAN to create a unified network architecture.
This combination addresses all of the challenges:
Limited Public IPs: Virtual WAN allows you to connect VNets using private IP addresses, reducing the need for public IPs.
Security: Azure Firewall provides robust network security, filtering traffic and protecting against threats.
Cost Optimization: Virtual WAN optimizes traffic routing between VNets, minimizing costs.
Why other options are less suitable:
Azure Bastion is used for secure management of VMs, but it doesn‘t address the other challenges.
Azure ExpressRoute is a dedicated private connection to Azure, but it may not be the most cost-effective option for smaller organizations.
Azure Load Balancer is used for load balancing traffic, but it doesn‘t provide the same level of network security as Azure Firewall.
Key Points:
This question tests your understanding of complex Azure networking scenarios.
It assesses your ability to choose the right combination of services to address multiple challenges simultaneously.
This scenario requires knowledge of both virtual network connectivity and network security in Azure.
6 / 42
6. Scenario:
Your company‘s security policy mandates the use of custom roles for managing access to sensitive Azure resources. You need to implement a solution that allows you to:
Define granular permissions for different user groups (e.g., developers, operators, administrators).
Ensure that users only have access to the specific resources and actions they need to perform their job functions.
Easily manage and update custom roles as your organization‘s needs evolve.
Question:
Which of the following approaches is the MOST suitable for creating and managing custom roles in Azure to meet your company‘s security requirements?
The most suitable answer is Create custom roles in the Azure portal using the JSON editor and assign them to security groups. Here‘s why:
Granular Permissions: The Azure portal‘s JSON editor allows you to define custom roles with precise permissions based on resource actions and data actions. This ensures that users have only the necessary access for their specific roles.
Ease of Management: The Azure portal provides a user-friendly interface for creating, editing, and assigning custom roles. This makes it easier to manage and update roles as your organization‘s needs change.
Security Groups: Assigning custom roles to security groups simplifies role management and ensures consistent permissions for all members of a group.
Why other options are less suitable:
Built-in roles may not offer the level of granularity required for your company‘s security policy.
While PowerShell and Azure CLI offer flexibility, they require scripting knowledge and may not be as user-friendly as the Azure portal for ongoing role management.
Azure Blueprints are great for defining and deploying standard configurations, but they are less flexible than directly creating and managing custom roles in the portal.
The most suitable answer is Create custom roles in the Azure portal using the JSON editor and assign them to security groups. Here‘s why:
Granular Permissions: The Azure portal‘s JSON editor allows you to define custom roles with precise permissions based on resource actions and data actions. This ensures that users have only the necessary access for their specific roles.
Ease of Management: The Azure portal provides a user-friendly interface for creating, editing, and assigning custom roles. This makes it easier to manage and update roles as your organization‘s needs change.
Security Groups: Assigning custom roles to security groups simplifies role management and ensures consistent permissions for all members of a group.
Why other options are less suitable:
Built-in roles may not offer the level of granularity required for your company‘s security policy.
While PowerShell and Azure CLI offer flexibility, they require scripting knowledge and may not be as user-friendly as the Azure portal for ongoing role management.
Azure Blueprints are great for defining and deploying standard configurations, but they are less flexible than directly creating and managing custom roles in the portal.
7 / 42
7. You have an Azure virtual machine named VM-01 that runs Windows Server 2019. You save VM-01 as a template named VM-Template to the Azure Resource Manager library. You plan to deploy a virtual machine named VM-02 from VM_Template, using Azure Portal
What can you configure during the deployment of VM-02?
After you deploy VM-01, you can save the template and reuse it to deploy other virtual machines, with the same configuration as VM-01. During the deployment of VM-02, you can change the resource group, if you need to.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/ps-template
Quick Preview:
After you deploy VM-01, you can save the template and reuse it to deploy other virtual machines, with the same configuration as VM-01. During the deployment of VM-02, you can change the resource group, if you need to.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/ps-template
Quick Preview:
8 / 42
8. You plan to deploy three Azure virtual machines named VM-01, VM-02, and VM-03. You need to ensure that at least two virtual machines are available if a single Azure datacenter becomes unavailable.
Which VM availability option should you choose?
The correct answer is: each VM deployed in a separate Availability Zone
Here’s why:
Availability Zones: Availability Zones are distinct locations within an Azure region.
1 They are physically separate and have independent power, cooling, and networking.
Requirement: You need at least two VMs to remain operational if one datacenter fails.
By deploying each VM in a separate Availability Zone, you ensure that if one Availability Zone (and its associated datacenter) experiences an outage, at least two of your VMs will remain operational in other Availability Zones.
Explanation of other options:
Single Availability Zone: If all VMs are in the same Availability Zone, a single datacenter failure will result in the loss of all three VMs.Single Availability Set: Availability Sets group VMs within the same datacenter for load balancing and fault domain isolation. However, they do not provide protection against datacenter failures.Each VM in a separate Availability Set: This provides some level of fault isolation within a datacenter but does not address the requirement of surviving a datacenter failure.In Summary
Deploying each VM in a separate Availability Zone provides the highest level of fault tolerance and ensures that your application can continue to function even if one datacenter experiences an outage.
Reference:
https://docs.microsoft.com/en-us/azure/availability-zones/az-overview#availability-zones
The correct answer is: each VM deployed in a separate Availability Zone
Here’s why:
Availability Zones: Availability Zones are distinct locations within an Azure region.
1 They are physically separate and have independent power, cooling, and networking.
Requirement: You need at least two VMs to remain operational if one datacenter fails.
By deploying each VM in a separate Availability Zone, you ensure that if one Availability Zone (and its associated datacenter) experiences an outage, at least two of your VMs will remain operational in other Availability Zones.
Explanation of other options:
Single Availability Zone: If all VMs are in the same Availability Zone, a single datacenter failure will result in the loss of all three VMs.Single Availability Set: Availability Sets group VMs within the same datacenter for load balancing and fault domain isolation. However, they do not provide protection against datacenter failures.Each VM in a separate Availability Set: This provides some level of fault isolation within a datacenter but does not address the requirement of surviving a datacenter failure.In Summary
Deploying each VM in a separate Availability Zone provides the highest level of fault tolerance and ensures that your application can continue to function even if one datacenter experiences an outage.
Reference:
https://docs.microsoft.com/en-us/azure/availability-zones/az-overview#availability-zones
9 / 42
9. You are currently running in your Azure subscription a virtual machine named VM-01. You install and configure a web server and a DNS server on VM-01. VM-01 has the inbound network security rules shown in the following exhibit:
Select the option that completes correctly the following sentence:
Internet users ………. .
NSG rules are processed from top to bottom, so Rule_1 is processed first, then Rule_2, Rule_3 … and so on.
DNS traffic is UDP/TCP port 53 and the first rule, Rule_1, denies this traffic, as configured action is Deny. Web traffic is HTTP port 80 (or it could be HTTPS), so this is TCP port 80 (or TCP 443 for HTTPS traffic). Web traffic is explicitly permitted by Rule_3.
Conclusion: considering current inbound rules, only traffic to web server running on VM-01 is allowed.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview
Quick Preview:
NSG rules are processed from top to bottom, so Rule_1 is processed first, then Rule_2, Rule_3 … and so on.
DNS traffic is UDP/TCP port 53 and the first rule, Rule_1, denies this traffic, as configured action is Deny. Web traffic is HTTP port 80 (or it could be HTTPS), so this is TCP port 80 (or TCP 443 for HTTPS traffic). Web traffic is explicitly permitted by Rule_3.
Conclusion: considering current inbound rules, only traffic to web server running on VM-01 is allowed.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview
Quick Preview:
10 / 42
10. You want to monitor the metrics and the logs of your Linux virtual machine VM-01.
Which of the following Azure services would you use for this task?
You can use extensions to configure diagnostics on your VMs to collect additional data metrics. The basic host metrics are directly available in Azure Monitor, but to see more granular and VM-specific metrics and logs information, you need to install an extension on the VM.
There are several extensions than can help to extend Azure Monitor Capabilities. Linux Diagnostic Extension (LAD) 3.0 is one of these extensions, specific to Linux VMs.
Azure Performance Diagnostics Extension is not a correct answer. This extension helps you troubleshoot performance issues that can affect a Windows or Linux virtual machine (VM). Supported troubleshooting scenarios include quick checks on known issues and best practices, and complex problems that involve slow VM performance or high usage of CPU, disk space, or memory.
Reference
Linux Diagnostic Extension (LAD) 3.0: https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/diagnostics-linux
Overview of Azure Monitor Agents: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/agents-overview
Azure Performance Diagnostics: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/performance-diagnostics
Quick Preview:
You can use extensions to configure diagnostics on your VMs to collect additional data metrics. The basic host metrics are directly available in Azure Monitor, but to see more granular and VM-specific metrics and logs information, you need to install an extension on the VM.
There are several extensions than can help to extend Azure Monitor Capabilities. Linux Diagnostic Extension (LAD) 3.0 is one of these extensions, specific to Linux VMs.
Azure Performance Diagnostics Extension is not a correct answer. This extension helps you troubleshoot performance issues that can affect a Windows or Linux virtual machine (VM). Supported troubleshooting scenarios include quick checks on known issues and best practices, and complex problems that involve slow VM performance or high usage of CPU, disk space, or memory.
Reference
Linux Diagnostic Extension (LAD) 3.0: https://docs.microsoft.com/en-us/azure/virtual-machines/extensions/diagnostics-linux
Overview of Azure Monitor Agents: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/agents-overview
Azure Performance Diagnostics: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/performance-diagnostics
Quick Preview:
11 / 42
11. Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
You have an Azure subscription named Subscription-Dev. Subscription-Dev contains a resource group named RG-01. RG-01 contains resources that were deployed by using templates.
You need to view the date and time when the resources were created in RG-01.
Solution: From the Subscriptions blade, you select the subscription, and then click Resource providers.
Does this meet the goal?
No, Resource providers will not help in this case. Instead, you can select Deployments inside RG-01 resource group and see a history of your deployments, inside the resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
No, Resource providers will not help in this case. Instead, you can select Deployments inside RG-01 resource group and see a history of your deployments, inside the resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
12 / 42
12. Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
You have an Azure subscription named Subscription-Dev. Subscription-Dev contains a resource group named RG-01. RG-01 contains resources that were deployed by using templates.
You need to view the date and time when the resources were created in RG-01.
Solution: From the Subscriptions blade, you select the subscription, and then click Programmatic deployment.
Does this meet the goal?
While you are in your RG-01 resource group blade, click Deployments. You will be able to see a history of your deployments for RG-01 resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
While you are in your RG-01 resource group blade, click Deployments. You will be able to see a history of your deployments for RG-01 resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
13 / 42
13. Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
You have an Azure subscription named Subscription-Dev. Subscription-Dev contains a resource group named RG-01. RG-01 contains resources that were deployed by using templates.
You need to view the date and time when the resources were created in RG-01.
Solution: From the RG-01 blade, you click Deployments.
Does this meet the goal?
While you are in your RG-01 resource group blade, click Deployments. You will be able to see a history of your deployments for RG-01 resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
While you are in your RG-01 resource group blade, click Deployments. You will be able to see a history of your deployments for RG-01 resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview:
14 / 42
14. Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
You have an Azure subscription named Subscription-Dev. Subscription-Dev contains a resource group named RG-01. RG-01 contains resources that were deployed by using templates.
You need to view the date and time when the resources were created in RG-01.
Solution: From the RG-01 blade, you click Automation script.
Does this meet the goal?
No, Automation script will not help in this case. Instead, you can select Deployments inside RG-01 resource group and see a history of your deployments, inside the resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview
No, Automation script will not help in this case. Instead, you can select Deployments inside RG-01 resource group and see a history of your deployments, inside the resource group.
Reference:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal
Quick Preview
15 / 42
15. You have an Azure subscription named Subscription1. In Subscription1, you create an Azure file share named share1.
You create a shared access signature (SAS) named SAS1 as shown in the following exhibit:
If on November 2, 2020, you run Microsoft Azure Storage Explorer on a computer that has an IP address of 134.92.112.1 and you use SAS1 to connect to the storage account, you ……………………….
The “Allowed IP Addresses” field doesn’t include the IP address of the computer you are using to access the storage account. The range defined is 134.92.112.10-134.92.112.50, so starting from .10 in the last octet and up to .50, while the computer IP address is 134.92.112.1, so .1 in the last octet.
The “Allowed IP Addresses” field doesn’t include the IP address of the computer you are using to access the storage account. The range defined is 134.92.112.10-134.92.112.50, so starting from .10 in the last octet and up to .50, while the computer IP address is 134.92.112.1, so .1 in the last octet.
16 / 42
16. You have an Azure subscription that contains the resources shown in the following table:
You need to configure Azure Backup reports for Recovery-Vault-1.You are configuring the Diagnostics settings for the AzureBackupReports log.
Which Log Analytics workspaces can you use for the Azure Backup reports of Recovery-Vault-1?
The Log analytics Workspace is independent of the location or subscription.
Reference:
https://docs.microsoft.com/en-us/azure/backup/configure-reports
Quick Preview:
The Log analytics Workspace is independent of the location or subscription.
Reference:
https://docs.microsoft.com/en-us/azure/backup/configure-reports
Quick Preview:
17 / 42
17. You have deployed in Azure an application App1, on two Azure virtual machines named VM1 and VM2. You plan to implement an Azure Availability Set for App1. The solution must ensure that App1 is available during planned maintenance of the servers hosting VM1 and VM2.
What should you include in the Availability Set?
From time to time, Microsoft runs planned maintenance events in order to update their hardware and software. Sometimes, the servers need to be rebooted during the maintenance events, which means that VMs running on these servers will be rebooted as well.
In order to avoid having both VMs rebooted at the same time, you can include two update domains in your availability set configuration. Each VM will be part of a different update domain. A rebooted update domain is given 30 minutes to recover before maintenance is initiated on a different update domain.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/manage-availability
Quick Preview:
From time to time, Microsoft runs planned maintenance events in order to update their hardware and software. Sometimes, the servers need to be rebooted during the maintenance events, which means that VMs running on these servers will be rebooted as well.
In order to avoid having both VMs rebooted at the same time, you can include two update domains in your availability set configuration. Each VM will be part of a different update domain. A rebooted update domain is given 30 minutes to recover before maintenance is initiated on a different update domain.
Reference:
https://docs.microsoft.com/en-us/azure/virtual-machines/manage-availability
Quick Preview:
19 / 42
19. You have an Azure subscription named Subscription-Prod that contains a resource group named RG-01.
In RG-01, you create an internal load balancer named LB-01. You need to ensure that an administrator named Admin-01 can manage LB-01 and is allowed to add a backend pool to LB-01. The solution must follow the principle of least privilege.
Which role should you assign to Admin-01 ?
The Network Contributor role lets you manage networks, but not access them. The Network Contributor role includes the Microsoft.Network/* action, so any action included in Microsoft.Network provider. When you assign the Network Contributor role to Admin-01, the exact permission (action) that will allow Admin-01 to create a backend pool is the following:
Microsoft.Network/loadBalancers/backendAddressPools/write
Action description as presented in the official documentation: This action will allow Admin-01 to create a load balancer backend address pool or update an existing load balancer backend address pool.
But in order to create the backend pool, is not enough to have Network Contributor access to the load balancer itself.
You also need read access over the Virtual Network, and the Virtual Machines you have to attach to the backend pool. And additionally you need some write permissions like Microsoft.Network/virtualNetworks/subnets/join/action to join the Vms to the backend pool.
So the least privilege role you can assign to Admin-01 is Network Contributor on RG-01.
Reference:
https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftnetwork
Quick Preview:
The Network Contributor role lets you manage networks, but not access them. The Network Contributor role includes the Microsoft.Network/* action, so any action included in Microsoft.Network provider. When you assign the Network Contributor role to Admin-01, the exact permission (action) that will allow Admin-01 to create a backend pool is the following:
Microsoft.Network/loadBalancers/backendAddressPools/write
Action description as presented in the official documentation: This action will allow Admin-01 to create a load balancer backend address pool or update an existing load balancer backend address pool.
But in order to create the backend pool, is not enough to have Network Contributor access to the load balancer itself.
You also need read access over the Virtual Network, and the Virtual Machines you have to attach to the backend pool. And additionally you need some write permissions like Microsoft.Network/virtualNetworks/subnets/join/action to join the Vms to the backend pool.
So the least privilege role you can assign to Admin-01 is Network Contributor on RG-01.
Reference:
https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles
https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftnetwork
Quick Preview:
20 / 42
20.
You have a .NET Core application running in Azure App Services. You are expecting a huge influx of traffic to your application in the coming days. When your application experiences this spike in traffic, you want to detect any anomalies such as request errors or failed queries immediately. What service can you use to assure that you know about these types of errors related to your .NET application immediately?
Live metrics stream includes such information as the number of incoming requests, the duration of those requests, and any failures that occur. You can also inspect critical performance metrics such as processor and memory.
Live metrics stream includes such information as the number of incoming requests, the duration of those requests, and any failures that occur. You can also inspect critical performance metrics such as processor and memory.
21 / 42
21.
You have a general purpose v1 storage account named storageaccount1 that has a private container named container1. You need to allow read access to the data inside container1, but only within a 14 day window. How do you accomplish this?
Create a shared access signature (SAS)
A shared access signature (SAS) is a URI that grants time-limited access to a specific resource in your storage account. By setting the appropriate permissions and expiry time in the SAS, you can allow read access to the data in container1 for a 14-day period.
Here’s how to create a SAS:
Generate SAS Token: Use the Azure portal, Azure CLI, or Azure PowerShell to generate a SAS token with the desired permissions (read) and expiry time (14 days).Share the SAS URI: Share the generated SAS URI with the intended users. They can use this URI to access the data in container1 within the specified time frame.Key advantages of using SAS:
Fine-grained control: You can precisely control who can access the data, what actions they can perform, and for how long.Security: By limiting access to a specific time period, you can mitigate security risks.Flexibility: SAS tokens can be generated for various resources and permissions, providing flexibility in sharing access.Note: While upgrading to general-purpose v2 storage account can offer additional features and performance improvements, it’s not necessary for this specific scenario. The SAS approach provides a more targeted and secure solution for granting temporary access to the data.
Create a shared access signature (SAS)
A shared access signature (SAS) is a URI that grants time-limited access to a specific resource in your storage account. By setting the appropriate permissions and expiry time in the SAS, you can allow read access to the data in container1 for a 14-day period.
Here’s how to create a SAS:
Generate SAS Token: Use the Azure portal, Azure CLI, or Azure PowerShell to generate a SAS token with the desired permissions (read) and expiry time (14 days).Share the SAS URI: Share the generated SAS URI with the intended users. They can use this URI to access the data in container1 within the specified time frame.Key advantages of using SAS:
Fine-grained control: You can precisely control who can access the data, what actions they can perform, and for how long.Security: By limiting access to a specific time period, you can mitigate security risks.Flexibility: SAS tokens can be generated for various resources and permissions, providing flexibility in sharing access.Note: While upgrading to general-purpose v2 storage account can offer additional features and performance improvements, it’s not necessary for this specific scenario. The SAS approach provides a more targeted and secure solution for granting temporary access to the data.
23 / 42
23. You have an Azure subscription that contains the virtual machines shown in the following table.
You deploy a load balancer that has the following configurations:
Name: LB1
Type: Internal
SKU: Standard
Virtual network: VNET1
You need to ensure that you can add VM1 and VM2 to the backend pool of LB1.
Solution: You create a Basic SKU public IP address, associate the address to the network interface of VM1, and then start VM1.
Does this meet the goal?
You can only attach virtual machines in the same region and that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network.
You can only attach virtual machines in the same region and that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network.
24 / 42
24. You have an Azure subscription that contains the virtual machines shown in the following table.
You deploy a load balancer that has the following configurations:
Name: LB1
Type: Internal
SKU: Standard
Virtual network: VNET1
You need to ensure that you can add VM1 and VM2 to the backend pool of LB1.
Solution: You create a Standard SKU public IP address, associate the address to the network interface of VM1, and then stop VM2.
Does this meet the goal?
You can only attach virtual machines in the same region and that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network.
You can only attach virtual machines in the same region and that have a standard SKU public IP configuration or no public IP configuration. All IP configurations must be on the same virtual network.
25 / 42
25. You have an Azure subscription that contains the virtual machines shown in the following table.
You deploy a load balancer that has the following configurations:
Name: LB1
Type: Internal
SKU: Standard
Virtual network: VNET1
You need to ensure that you can add VM1 and VM2 to the backend pool of LB1.
Solution: You create two Standard public IP addresses and associate a Standard SKU public IP address to the network interface of each virtual machine.
Does this meet the goal?
To add a new standard SKU public IP address to VM2, first you need to disassociate the existing Basic IP address.
To add a new standard SKU public IP address to VM2, first you need to disassociate the existing Basic IP address.
28 / 42
28.
You have an Azure subscription. You need to transfer 34TB of data from an on-premise Windows 2016 server to your Azure storage account. You need to ensure that the data transfer has zero impact on the network, preserves your existing drives and is the fastest and most secure method. What should be your first step?
The Microsoft Azure Data Box cloud solution lets you send terabytes of data into and out of Azure in a quick, inexpensive, and reliable way.
https://docs.microsoft.com/en-us/azure/databox/data-box-overview
INCORRECT ANSWERS:
Start an Import Job via the Azure Portal This is required for disk shipment that does not support the volume of data in the question.
Open a ticket with Microsoft Support MS support not required.
Prepare your hard drives using the WAImportExport tool – This is required for disk shipment that does not support the volume of data in the question.
The Microsoft Azure Data Box cloud solution lets you send terabytes of data into and out of Azure in a quick, inexpensive, and reliable way.
https://docs.microsoft.com/en-us/azure/databox/data-box-overview
INCORRECT ANSWERS:
Start an Import Job via the Azure Portal This is required for disk shipment that does not support the volume of data in the question.
Open a ticket with Microsoft Support MS support not required.
Prepare your hard drives using the WAImportExport tool – This is required for disk shipment that does not support the volume of data in the question.
31 / 42
31. You have an Azure subscription that contains the file shares shown in the following table.
You have the on-premises file shares shown in the following table.
You create an Azure file sync group named Sync1 and perform the following actions:
Add share1 as the cloud endpoint for Sync1.
Add data1 as a server endpoint for Sync1.
Register Server1 and Server2 to Sync1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
1. You can add share3 as an additional cloud endpoint for Sync1
2. You can add data2 as an additional server endpoint for Sync1
3. You can add data3 as an additional server endpoint for Sync1
A) Yes, Yes, Yes
B) Yes, No, No
C) No, Yes, No
D) Yes, Yes, No
E) No, Yes, Yes
1. A sync group must contain one cloud endpoint, which represents an Azure file share and one or more server endpoints.
2. Data2 is located on Server2 which is registered to Sync1.
3. Data3 is located on Server3 which is not registered to Sync1.
https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deployment-guide?tabs=azure-portal%2Cproactive-portal#create-a-sync-group-and-a- cloud-endpoint
1. A sync group must contain one cloud endpoint, which represents an Azure file share and one or more server endpoints.
2. Data2 is located on Server2 which is registered to Sync1.
3. Data3 is located on Server3 which is not registered to Sync1.
https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deployment-guide?tabs=azure-portal%2Cproactive-portal#create-a-sync-group-and-a- cloud-endpoint
33 / 42
33. You have an Azure subscription that contains a resource group named TestRG.
You use TestRG to validate an Azure deployment. TestRG contains the following resources:
You need to delete TestRG.
What should you do first?
You can’t delete a vault that contains backup data. You must remove the delete locks before trying to delete a resource group.
When you delete a resource group, all of its resources are also deleted. Deleting a resource group deletes all of its template deployments and currently stored operations.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group?tabs=azure-powershell
INCORRECT ANSWERS:
Modify the backup configurations of VM1 and modify the resource lock type of VNET1 You need to delete the lock, changing the lock type will become from delete to read-only.
Turn off VM1 and remove the resource lock from VNET1 You need to also clear data from Vault.
Turn off VM1 and delete all data in Vault1 You need to delete the lock as well.
You can’t delete a vault that contains backup data. You must remove the delete locks before trying to delete a resource group.
When you delete a resource group, all of its resources are also deleted. Deleting a resource group deletes all of its template deployments and currently stored operations.
https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/delete-resource-group?tabs=azure-powershell
INCORRECT ANSWERS:
Modify the backup configurations of VM1 and modify the resource lock type of VNET1 You need to delete the lock, changing the lock type will become from delete to read-only.
Turn off VM1 and remove the resource lock from VNET1 You need to also clear data from Vault.
Turn off VM1 and delete all data in Vault1 You need to delete the lock as well.
34 / 42
34. You deploy an Azure Kubernetes Service (AKS) cluster that has the network profile shown in the following exhibit.
In which subnet, the services in the AKS cluster will be assigned an IP address?
The –service-cidr is used to assign internal services in the AKS cluster an IP address.
https://docs.microsoft.com/en-us/azure/aks/configure-kubenet
INCORRECT ANSWERS:
10.244.0.0/16 – pod-cidr – The pod IP address range is used to assign a /24 address space to each node in the cluster.
172.17.0.1/16 Docker Bridge CIDR It lets the AKS nodes communicate with the underlying management platform.
The –service-cidr is used to assign internal services in the AKS cluster an IP address.
https://docs.microsoft.com/en-us/azure/aks/configure-kubenet
INCORRECT ANSWERS:
10.244.0.0/16 – pod-cidr – The pod IP address range is used to assign a /24 address space to each node in the cluster.
172.17.0.1/16 Docker Bridge CIDR It lets the AKS nodes communicate with the underlying management platform.
35 / 42
35. You deploy an Azure Kubernetes Service (AKS) cluster that has the network profile shown in the following exhibit.
In which subnet, the containers will be assigned an IP address?
The –pod-cidr -This address range must be large enough to accommodate the number of nodes that you expect to scale up to. You can’t change this address range once the cluster is deployed if you need more addresses for additional nodes. The pod IP address range is used to assign a /24 address space to each node in the cluster.
https://docs.microsoft.com/en-us/azure/aks/configure-kubenet
INCORRECT ANSWERS:
10.0.0.0/16 Service CIDR It is used to assign internal services in the AKS cluster an IP address.
172.17.0.1/16 Docker Bridge CIDR It lets the AKS nodes communicate with the underlying management platform.
The –pod-cidr -This address range must be large enough to accommodate the number of nodes that you expect to scale up to. You can’t change this address range once the cluster is deployed if you need more addresses for additional nodes. The pod IP address range is used to assign a /24 address space to each node in the cluster.
https://docs.microsoft.com/en-us/azure/aks/configure-kubenet
INCORRECT ANSWERS:
10.0.0.0/16 Service CIDR It is used to assign internal services in the AKS cluster an IP address.
172.17.0.1/16 Docker Bridge CIDR It lets the AKS nodes communicate with the underlying management platform.
36 / 42
36. You have an Azure virtual machine named VM1 that connects to a virtual network named VNet1. VM1 has the following configurations:
Subnet: 10.0.0.0/24
Availability set: AVSet
Network security group (NSG): None
Private IP address: 10.0.0.4 (dynamic)
Public IP address: 40.90.219.6 (dynamic)
You deploy a standard, Internet-facing load balancer named slb1.
You need to configure slb1 to allow connectivity to VM1.
Which changes should you apply to VM1 as you configure slb1?
Check
A public load balancer can provide outbound connections for virtual machines (VMs) inside your virtual network. These connections are accomplished by translating their private IP addresses to public IP addresses. You need to have a static IP address for your VM.
NSGs are used to explicitly permit allowed traffic. If you do not have an NSG on a subnet or NIC of your virtual machine resource, traffic is not allowed to reach this resource.
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview
A public load balancer can provide outbound connections for virtual machines (VMs) inside your virtual network. These connections are accomplished by translating their private IP addresses to public IP addresses. You need to have a static IP address for your VM.
NSGs are used to explicitly permit allowed traffic. If you do not have an NSG on a subnet or NIC of your virtual machine resource, traffic is not allowed to reach this resource.
https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-overview
37 / 42
37. You have an Azure subscription that contains the resources shown in the following table.
You need to create a network interface named NIC1.
In which location can you create NIC1?
Before creating a network interface, you must have an existing virtual network in the same location and subscription you create a network interface in.
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface
INCORRECT ANSWERS:
The location of NIC must be virtual network location only. Any option other than East US is wrong.
Before creating a network interface, you must have an existing virtual network in the same location and subscription you create a network interface in.
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface
INCORRECT ANSWERS:
The location of NIC must be virtual network location only. Any option other than East US is wrong.
38 / 42
38. You plan to use Azure Network Watcher to perform the following tasks:
Task1: Identify a security rule that prevents a network packet from reaching an Azure virtual machine.
Task2: Validate outbound connectivity from an Azure virtual machine to an external host.
Which feature should you use for task2?
The connection troubleshoot capability enables you to test a connection between a VM and another VM, an FQDN, a URI, or an IPv4 address. The test returns similar information returned when using the connection monitor capability, but tests the connection at a point in time, rather than monitoring it over time, as connection monitor does
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview
INCORRECT ANSWERS:
Next hop — Next hop helps you determine if traffic is being directed to the intended destination, or whether the traffic is being sent nowhere.
NSG flow logs — NSG flow logs is a feature of Azure Network Watcher that allows you to log information about IP traffic flowing through an NSG.
Traffic Analytics It provides visibility into user and application activity in cloud networks.
The connection troubleshoot capability enables you to test a connection between a VM and another VM, an FQDN, a URI, or an IPv4 address. The test returns similar information returned when using the connection monitor capability, but tests the connection at a point in time, rather than monitoring it over time, as connection monitor does
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-monitoring-overview
INCORRECT ANSWERS:
Next hop — Next hop helps you determine if traffic is being directed to the intended destination, or whether the traffic is being sent nowhere.
NSG flow logs — NSG flow logs is a feature of Azure Network Watcher that allows you to log information about IP traffic flowing through an NSG.
Traffic Analytics It provides visibility into user and application activity in cloud networks.
39 / 42
39. You have an app named App1 that is installed on two Azure virtual machines named VM1 and VM2. Connections to App1 are managed by using an Azure Load Balancer.
The effective network security configurations for VM2 are shown in the following exhibit.
You discover that connections to App1 from 131.107.100.50 over TCP port 443 fail.
You verify that the Load Balancer rules are configured correctly.
You need to ensure that connections to App1 can be established successfully from 131.107.100.50 over TCP port 443.
Solution: You create an inbound security rule that denies all traffic from the 131.107.100.50 source and has a cost of 64999.
Does this meet the goal?
40 / 42
40. You have an app named App1 that is installed on two Azure virtual machines named VM1 and VM2. Connections to App1 are managed by using an Azure Load Balancer.
The effective network security configurations for VM2 are shown in the following exhibit.
You discover that connections to App1 from 131.107.100.50 over TCP port 443 fail.
You verify that the Load Balancer rules are configured correctly.
You need to ensure that connections to App1 can be established successfully from 131.107.100.50 over TCP port 443.
Solution: You delete the BlockAllOther441 inbound security rule.
Does this meet the goal?
41 / 42
41. You have an Azure virtual machine that is protected by Azure Backup.
One week ago, two files were deleted from the virtual machine.
You need to restore the deleted files to an on-premises Windows Server 2016 computer as quickly as possible.
Which four actions should you perform in sequence?
Azure Backup provides the capability to restore Azure virtual machines (VMs) and disks from Azure VM backups, also known as recovery points. Restoring files and folders is available only for Azure VMs deployed using the Resource Manager model and protected to a Recovery Services vault.
To restore files or folders from the recovery point, go to the virtual machine and perform the following steps:
Sign in to the Azure portal and in the left pane, select Virtual machines. From the list of virtual machines, select the virtual machine to open that virtual machine’s dashboard.
In the virtual machine’s menu, select Backup to open the Backup dashboard.
In the Backup dashboard menu, select File Recovery.
From the Select recovery point drop-down menu, select the recovery point that holds the files you want.
Select Download Executable or Download Script to download the software used to copy files from the recovery point.
Copy the files using File Explorer!
https://docs.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm
Azure Backup provides the capability to restore Azure virtual machines (VMs) and disks from Azure VM backups, also known as recovery points. Restoring files and folders is available only for Azure VMs deployed using the Resource Manager model and protected to a Recovery Services vault.
To restore files or folders from the recovery point, go to the virtual machine and perform the following steps:
Sign in to the Azure portal and in the left pane, select Virtual machines. From the list of virtual machines, select the virtual machine to open that virtual machine’s dashboard.
In the virtual machine’s menu, select Backup to open the Backup dashboard.
In the Backup dashboard menu, select File Recovery.
From the Select recovery point drop-down menu, select the recovery point that holds the files you want.
Select Download Executable or Download Script to download the software used to copy files from the recovery point.
Copy the files using File Explorer!
https://docs.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm
Your score is
The average score is 56%
Restart quiz