AZ-700 Online Practice Questions and Answers

Correct Answer: A

Expressroute Local supports this particular networking scenario for two reasons.

1) The Washington DC peering location has East US as its Local Azure region. So, you don't need access to all the Geopolitical locations in order to connect the on-prem DC to Azure. Which means you won't necessarily need Expressroute

standard.

2) ExpressRoute Local is a more economical solution compared to the standard.

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-faqs#what-are-the-benefits-of-expressroute-local

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-locations-providers#global-commercial-azure

Correct Answer: B

Reference: https://docs.microsoft.com/en-us/azure/expressroute/expressroute-global-reach

Correct Answer: AH

None of these resources has a requirement for dedicated virtual network. So, you can deploy all these resources in a single virtual network.

Azure virtual machine must be deployed to a subnet. So, you need at least one subnet for virtual machine.

Azure app service is delegate to create resources in the virtual network. So you need configure vNet integration for Azure app service. An integration subnet is required to integrate Azure App service with virtual network.

You need a dedicated subnet called as gateway subnet for virtual network gateway.

SQL Managed Instance is placed inside the Azure virtual network and the subnet that's dedicated to managed instances.

So, in total you need a minimum of 4 subnets.

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-for-azure-services#services-that-can-be- deployed-into-a-virtual-network

Correct Answer: A

Use private endpoints for Azure Storage

You can use private endpoints for your Azure Storage accounts to allow clients on a virtual network (VNet) to securely access data over a Private Link. The private endpoint uses a separate IP address from the VNet address space for each

storage account service.

Plan:

Stage 1: Create a virtual network and subnet

Stage 2: Create a private endpoint

Stage 1: Create a virtual network and subnet

Step 1: Sign in to the Azure portal.

Step 2: In the search box at the top of the portal, enter Virtual network. In the search results, select Virtual networks.

Step 3: Select + Create in Virtual networks.

Step 4: In the Basics tab of Create virtual network, enter or select the following information.

Subscription -Select your subscription.

Resource group - Select Create new.

Enter SomeName in Name and select OK.

Instance details

Name - Enter myVNet for example

Region - Select West Europe.

Step 5: Select Next: IP Addresses or the IP Addresses tab.

Step 6: Select the IP Addresses tab or select Next: IP Addresses at the bottom of the page.

Step 7: In the IP Addresses tab, enter the following information:

* IPv4 address space - Enter 10.1.0.0/16

Step 8: Select Add subnet. In Edit subnet, enter the following information:

Subnet name - Enter mySubnet

Subnet address range - Enter 10.1.1.0/24 (as specified in the question)

Step 9: For the subnet: Select the Review + create tab or select the Review + create button.

Step 10: For the Virtual network: Select the Review + create tab or select the Review + create button.

Stage 2: Create a private endpoint

Step 1: In the search box at the top of the portal, enter Private endpoint. Select Private endpoints.

Step 2: Select + Create in Private endpoints.

Step 3: In the Basics tab of Create a private endpoint, enter or select the following information.

*

Storage subresource - storage12345678.privatelink.blob.core.windows.net

*

Private DNS integration.

Integrate with private DNS zone - Leave the default Yes.

*

Private DNS Zone

Leave the default (New) privatelink.blob.core.windows.net.

Step 4: Select Next: Resource.

Step 5: In the Resource pane, leave the defaults.

Step 6: Select Next: Virtual Network.

Step 7: In Virtual Network, enter or select the following information.

Virtual network - Select the virtual network you created in stage 1.

Subnet - Select the subnet you created in stage 1.

Step 8: Select Next: DNS.

Step 9: Leave the defaults in DNS. Select Next: Tags, then Next: Review + create.

Step 10: Select Create.

Reference: https://learn.microsoft.com/en-us/azure/storage/common/storage-private-endpoints https://learn.microsoft.com/en-us/azure/private-link/create-private-endpoint-portal

Correct Answer:

Reference: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-about

Correct Answer:

Box 1: 2

All network interfaces assigned to an application security group have to exist in the same virtual network that the first network interface assigned to the application security group is in.

We need one application security group for each of the two virtual networks.

Box 2: 3

One network assignment in VNet1. Two network assignments in VNET2.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/application-security-groups

Correct Answer:

Box 1: No

VM1, which is hosting site1.contoso.com, is located in East US. The VM1 endpoint status is degraded. Endpoint monitoring health checks are failing. The endpoint isn't included in DNS responses and doesn't receive traffic.

When an endpoint has a Degraded status, it's no longer returned in response to DNS queries. Instead, an alternative endpoint is chosen and returned. The traffic-routing method configured in the profile determines how the alternative

endpoint is chosen.

Priority. Endpoints form a prioritized list. The first available endpoint on the list is always returned. If an endpoint status is Degraded, then the next available endpoint is returned.

The user will connect to site2.us.contoso.com instead.

Box 2: No

VM3, which is hosting site2.contoso.com, is located in in East US. The VM3 endpoint status is CheckingEndpoint. The endpoint is monitored, but the results of the first probe haven't been received yet. CheckingEndpoint is a temporary state

that usually occurs immediately after adding or enabling an endpoint in the profile. An endpoint in this state is included in DNS responses and can receive traffic.

User will connect to site2.contoso.com, not to site2.uk.contoso.com

Box 3: No

VM3, which is hosting site2.contoso.com, is located in in East US. The VM1 endpoint status is CheckingEndpoint, which is OK (see above).

User will connect to site2.contoso.com, not to site2.japan.contoso.com

Reference:

https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring

Correct Answer:

Explanation:

Box 1: An additional subnet

Regional virtual network integration: When you connect to virtual networks in the same region, you must have a dedicated subnet in the virtual network you're integrating with.

Box 2: A VPN gateway

Gateway-required virtual network integration: When you connect directly to virtual networks in other regions or to a classic virtual network in the same region, you need an Azure Virtual Network gateway created in the target virtual network.

Note: If your app is in an App Service Environment, it's already in a virtual network and doesn't require use of the VNet integration feature to reach resources in the same virtual network.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/overview-vnet-integration

Correct Answer:

Box 1: 3

Subnet address range: The range must be within the address space you entered for the virtual network. The smallest range you can specify is /29, which provides eight IP addresses for the subnet. Azure reserves the first and last address in

each subnet for protocol conformance. Three more addresses are reserved for Azure service usage. As a result, a virtual network with a subnet address range of /29 has only three usable IP addresses.

Box 2: 32

We can make 32 /29 subnets of a /24 IPv4 address space.

Reference:

https://learn.microsoft.com/en-us/azure/virtual-network/manage-virtual-network

Correct Answer: