Free Microsoft AZ-700 Exam Questions (page: 8)

View Related Case Study

DRAG DROP (Drag and Drop is not supported)

You have an on-premises network.

You have an Azure subscription that contains a virtual network named VNet1. VNet1 contains an ExpressRoute gateway.

You need to connect VNet1 to the on-premises network by using an ExpressRoute circuit.

Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Step 1: Create an ExpressRoute circuit
Create an ExpressRoute circuit as follows:

1. Run the following PowerShell command:

New-AzExpressRouteCircuit -Name <<circuit-name>> -ResourceGroupName <<resource-group>> -Location <<location>> -SkuTier <<sku-tier>> -SkuFamily <<sku-family>> -ServiceProviderName <<service-provider- name>> -PeeringLocation <<peering-location>> -BandwidthInMbps <<bandwidth-in-mbps>>

2. Send the ServiceKey for the new circuit to the service provider.

3. Wait for the provider to provision the circuit. To verify the provisioning state of a circuit, run the following PowerShell command:

Get-AzExpressRouteCircuit -Name <<circuit-name>> -ResourceGroupName <<resource-group>>

Step 2: Send the service key to your connectivity provider

Step 3: Configure Azure private peering
You can use either Microsoft peering or Private peering

Use the following example to configure Azure private peering for your circuit:

Add-AzExpressRouteCircuitPeeringConfig -Name "AzurePrivatePeering" -ExpressRouteCircuit $ckt -

PeeringType AzurePrivatePeering -PeerASN 100 -PrimaryPeerAddressPrefix "10.0.0.0/30" - SecondaryPeerAddressPrefix "10.0.0.4/30" -VlanId 200

Add-AzExpressRouteCircuitPeeringConfig -Name "AzurePrivatePeering" -ExpressRouteCircuit $ckt - PeeringType AzurePrivatePeering -PeerASN 100 -PrimaryPeerAddressPrefix "3FFE:FFFF:0:CD30::/126" - SecondaryPeerAddressPrefix "3FFE:FFFF:0:CD30::4/126" -VlanId 200 -PeerAddressType IPv6

Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt

Step 4: Create a connection from VNet1 to the ExpressRoute circuit Run the following PowerShell commands to link your private VNet(s) to the ExpressRoute circuit.

$circuit = Get-AzExpressRouteCircuit -Name <<circuit-name>> -ResourceGroupName <<resource-group>> $gw = Get-AzVirtualNetworkGateway -Name <<gateway-name>> -ResourceGroupName <<resource-group>> New-AzVirtualNetworkGatewayConnection -Name <<connection-name>> -ResourceGroupName <<resource- group>> -Location <<location> -VirtualNetworkGateway1 $gw -PeerId $circuit.Id -ConnectionType ExpressRoute


Reference:

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-arm



View Related Case Study

You have three on-premises networks.

You have an Azure subscription that contains a Basic Azure virtual WAN. The virtual WAN contains a single virtual hub and a virtual network gateway that is limited to a throughput of 1 Gbps.

The on-premises networks connect to the virtual WAN by using Site-to-Site (S2S) VPN connections.

You need to increase the throughput of the virtual WAN to 3 Gbps. The solution must minimize administrative effort.

What should you do?

  1. Upgrade the virtual WAN to the Standard SKU.
  2. Add an additional VPN gateway to the Azure subscription.
  3. Create an additional virtual hub.
  4. Increase the number of gateway scale units.

Answer(s): D

Explanation:

Increase the scale units.
Note: VPN S2S Scale Unit, $0.361/hour, 500 Mbps per Scale Unit, per Deployment Hour Incorrect:
Not A: Type: Basic or Standard. Select Standard. If you select Basic, understand that Basic virtual WANs can only contain Basic hubs. Basic hubs can only be used for site-to-site connections.


Reference:

https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-site-to-site-portal https://azure.microsoft.com/en-us/pricing/details/virtual-wan/



View Related Case Study

You have 10 on-premises networks that are connected by using a 3rd party Software Defined Wide Area Network (SD-WAN) solution. You have an Azure subscription that contains five virtual networks.

You plan to connect the Azure virtual networks and the on-premises networks by using an Azure Virtual WAN with a single virtual WAN hub.

You need to ensure that the Azure Virtual WAN can act as a node in the 3rd party SD-WAN solution.

What should you include in the solution?

  1. An Azure Virtual WAN ExpressRoute gateway
  2. A Network Virtual Appliance (NVA)
  3. A Site to site gateway (VPN gateway)
  4. A Point to site gateway (User VPN gateway)

Answer(s): B

Explanation:

About NVAs in a Virtual WAN hub
Customers can deploy select Network Virtual Appliances (NVAs) directly into a Virtual WAN hub in a solution that is jointly managed by Microsoft Azure and third-party Network Virtual Appliance vendors.
Key benefits
When an NVA is deployed into a Virtual WAN hub, it can serve as a third-party gateway with various functionalities. It could serve as an SD-WAN gateway, Firewall, or a combination of both.


Reference:

https://learn.microsoft.com/en-us/azure/virtual-wan/about-nva-hub



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

You have the Azure resources shown in the following table.



You need to link VNet2 to Circuit1.

What should you create in each subscription? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: An ExpressRoute circuit connection authorization
Sub1:
Circuit owner operations
To create a connection authorization

The circuit owner creates an authorization, which creates an authorization key to be used by a circuit user to connect their virtual network gateways to the ExpressRoute circuit. An authorization is valid for only one connection.

Note: Administration - About circuit owners and circuit users The 'circuit owner' is an authorized Power User of the ExpressRoute circuit resource. The circuit owner can create authorizations that can be redeemed by 'circuit users'. Circuit users are owners of virtual network gateways that aren't within the same subscription as the ExpressRoute circuit. Circuit users can redeem authorizations (one authorization per virtual network).

The circuit owner has the power to modify and revoke authorizations at any time. Revoking an authorization results in all link connections being deleted from the subscription whose access was revoked.

Box 2: An ExpressRoute circuit connection
Sub2:
Circuit user operations
The circuit user needs the resource ID and an authorization key from the circuit owner.

To redeem a connection authorization

1. Select the + Create a resource button. Search for Connection and select Create.

2. Make sure the Connection type is set to ExpressRoute. Select the Resource group and Location, then select OK in the Basics page.

3. In the Settings page, Select the Virtual network gateway and check the Redeem authorization check box. Enter the Authorization key and the Peer circuit URI and give the connection a name. Select OK.

4. Review the information in the Summary page and select OK.

Note: Connect a VNet to a circuit - different subscription
You can share an ExpressRoute circuit across multiple subscriptions. The following figure shows a simple schematic of how sharing works for ExpressRoute circuits across multiple subscriptions.



Each of the smaller clouds within the large cloud is used to represent subscriptions that belong to different departments within an organization. Each of the departments within the organization uses their own subscription for deploying their services--but they can share a single ExpressRoute circuit to connect back to your on-premises network. A single department (in this example: IT) can own the ExpressRoute circuit. Other subscriptions within the organization may use the ExpressRoute circuit.


Reference:

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-linkvnet-portal-resource-manager



View Related Case Study

You have an on-premises datacenter and an Azure subscription.

You plan to implement ExpressRoute FastPath.

You need to create an ExpressRoute gateway. The solution must minimize downtime if a single Azure datacenter fails.

Which SKU should you use?

  1. ErGw1AZ
  2. High performance
  3. Ultra performance
  4. ErGw3AZ
  5. ErGw2AZ

Answer(s): D

Explanation:

Feature support by gateway SKU
The following table shows the features supported across each gateway type.



Zone-redundant gateway SKUs
You can also deploy ExpressRoute gateways in Azure Availability Zones. This configuration physically and logically separates them into different Availability Zones, protecting your on-premises network connectivity to Azure from zone-level failures.
Zone-redundant gateways use specific new gateway SKUs for ExpressRoute gateway.
ErGw1AZ
ErGw2AZ
*-> ErGw3AZ
Note: ExpressRoute virtual network gateways can use the following SKUs:
Standard
HighPerformance

UltraPerformance
ErGw1Az
ErGw2Az
ErGw3Az


Reference:

https://learn.microsoft.com/en-us/azure/expressroute/expressroute-about-virtual-network-gateways



Viewing page 8 of 75
Viewing questions 36 - 40 out of 369 questions



Post your Comments and Discuss Microsoft AZ-700 exam prep with other Community members:

AZ-700 Exam Discussions & Posts