You need direct connectivity from an on-premises network to SAP HANA (Large Instances). The solution must meet the following requirements: ✑ Minimize administrative effort. ✑ Provide the highest level of resiliency. What should you use?
Suggested Answer:C🗳️
The Azure network functionality used is: ✑ Azure virtual networks are connected to the ExpressRoute circuit that connects to your on-premises network assets. ✑ An ExpressRoute circuit that connects on-premises to Azure should have a minimum bandwidth of 1 Gbps or higher. This minimal bandwidth allows adequate bandwidth for the transfer of data between on-premises systems and systems that run on VMs. It also allows adequate bandwidth for connection to Azure systems from on-premises users. ✑ All SAP systems in Azure are set up in virtual networks to communicate with each other. Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture
Express Route cannot be used to DIRECTLY connect On-premise to HLI.
Answer is A
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture
ExpressRoute is a better option than ExpressRoute Global Reach in this case because it provides a private, dedicated connection between an on-premises network and Azure, which ensures the highest level of resiliency and security. With ExpressRoute, traffic never traverses the public internet, providing a more secure and reliable connection to SAP HANA (Large Instances). ExpressRoute Global Reach is used to connect two ExpressRoute circuits in different regions, which is not necessary in this scenario.
A. Microsoft introduced a new functionality called ExpressRoute Global Reach. Global Reach can be used for HANA Large Instances in two scenarios:
Enable direct access from on-premises to your HANA Large Instance units deployed in different regions
Enable direct communication between your HANA Large Instance units deployed in different regions
Express Route Global Reach
Microsoft introduced a new functionality called ExpressRoute Global Reach. Global Reach can be used for HANA Large Instances in two scenarios:
Enable direct access from on-premises to your HANA Large Instance units deployed in different regions
Enable direct communication between your HANA Large Instance units deployed in different regions
Direct Access from on-premises
In the Azure regions where Global Reach is offered, you can request enabling the Global Reach functionality for your ExpressRoute circuit that connects your on-premises network to the Azure virtual network that connects to your HANA Large Instance units as well.
C is correct. (ExpressRoute enables connectivity from your on-premises network to Microsoft cloud services. ExpressRoute Global Reach enables connectivity between your own on-premises networks through your existing ExpressRoute circuits, using Microsoft's global network.ExpressRoute enables connectivity from your on-premises network to Microsoft cloud services. ExpressRoute Global Reach enables connectivity between your own on-premises networks through your existing ExpressRoute circuits, using Microsoft's global network.)
ExpressRoute is a better option than ExpressRoute Global Reach in this case because it provides a private, dedicated connection between an on-premises network and Azure, which ensures the highest level of resiliency and security. With ExpressRoute, traffic never traverses the public internet, providing a more secure and reliable connection to SAP HANA (Large Instances). ExpressRoute Global Reach is used to connect two ExpressRoute circuits in different regions, which is not necessary in this scenario.
Ans is A.
ER without GR option can not route traffic from on-prem to HLI nets.
For ER without GR option to route traffic from on-prem to HLI nets must be implemented transitive routing by means of reverse-proxy\IPTables\AZFW
https://docs.microsoft.com/en-us/learn/modules/sap-hana-azure-compute-network-storage/7-workloads-azure-large-instances-routing-considerations
and
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture
A. ExpressRoute Global Reach
https://docs.microsoft.com/en-us/learn/modules/sap-hana-azure-compute-network-storage/7-workloads-azure-large-instances-routing-considerations
Microsoft used Express Route to connect HLI to customer's VNet.
So now going from the customer VNet to customer on-premises, it would be Express Route as well as it fulfills what is required. Express Route Global Reach when you are setting up a HSR from one HLI to another HLI sitting in a DR site.
From MS docs --> "HANA Large Instances networks are isolated from each other for security. By default, instances residing in
diferent regions do not communicate with each other, except for the dedicated storage replication.
However, to use HSR, inter-region communications are required. ExpressRoute Global Reach, IP routing tables, or proxies can be used to enable cross-regions HSR.
"
this question quite tricky.
- direct connectivity from on-premises network to HLI
ExpressRoute circuit that connects on-premises to Azure, but didn't mention HLI
Refer to https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture#direct-access-from-on-premises
If you use ExpressRoute Global Reach to enable direct access from on-premises to HLI units restrictions & permissions to access HLI units "need to be defined in firewalls" on the on-premises side
SAP HANA on Azure (Large Instances) can be accessed only through Azure VMs and the dedicated ExpressRoute connection, not directly from on-premises
Ans is A.
ER without GR option can not route traffic from on-prem to HLI nets.
For ER without GR option to route traffic from on-prem to HLI nets must be implemented transitive routing by means of reverse-proxy\IPTables\AZFW
https://docs.microsoft.com/en-us/learn/modules/sap-hana-azure-compute-network-storage/7-workloads-azure-large-instances-routing-considerations
and
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture
ExpressRoute Global Reach is the good answer, check the link https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-network-architecture#direct-access-from-on-premises
Answer : ExpressRoute correct Answer,
Express Route Global Reach is not correct option, Because ExpressRoute Global Reach. can be used for HANA Large Instances in two scenarios:
Enable direct access from on-premises to your HANA Large Instance units deployed in different regions
Enable direct communication between your HANA Large Instance units deployed in different regions
Direct Access from on-premises
In the Azure regions where Global Reach is offered, you can request enabling the Global Reach functionality for your ExpressRoute circuit that connects your on-premises network to the Azure virtual network that connects to your HANA Large Instance units as well. There are some cost implications for the on-premises side of your ExpressRoute circuit. For prices, check the prices for Global Reach Add-On. There are no additional costs for you related to the circuit that connects the HANA Large Instance unit(s) to Azure.
One ER to you azure account and one internal HANA express route. These cannot be used to connect to HLI directly from on-prem. Global reach allows direct connectivity from on-premise by connecting these 2 ER circuits. Answer is A.
This section is not available anymore. Please use the main Exam Page.AZ-120 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
McDee
Highly Voted 4 years, 3 months agotmtrg000
1 year, 6 months agomaybelline_ny
4 years, 2 months agoBhagirathi
Highly Voted 3 years, 10 months agostevethai
Most Recent 4 months, 3 weeks agoGabor_Jozsef
1 year, 3 months agotmtrg000
1 year, 6 months agokkrai
2 years, 5 months agod0bermannn
3 years agoKaiju
3 years, 7 months agogills
3 years, 8 months agoShub94
3 years, 9 months agoSteveChai
3 years, 8 months agod0bermannn
3 years agoimadedakir
3 years, 10 months agokktg
4 years, 1 month agokktg
4 years, 1 month agoRaghav7595
4 years, 1 month agoRakd
4 years, 1 month agopraveenkumarh1912
4 years, 2 months agoAynaras
4 years, 2 months agoAynaras
4 years, 2 months ago