HOTSPOT - You are planning the Azure network infrastructure for an SAP environment. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Hot Area:
Box 2: No - A design that's not supported is the segregation of the SAP application layer and the DBMS layer into different Azure virtual networks that aren't peered with each other. We recommend that you segregate the SAP application layer and DBMS layer by using subnets within an Azure virtual network instead of by using different Azure virtual networks.
Box 3: Yes - Be aware that network traffic between two peered Azure virtual networks is subject to transfer costs. Huge data volume that consists of many terabytes is exchanged between the SAP application layer and the DBMS layer. You can accumulate substantial costs if the SAP application layer and DBMS layer are segregated between two peered Azure virtual networks. Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general
No, Yes, Yes
NO because Although a possible configuration for segregating App and DB into different Peered Virtual Networks, it would be highly discouraged because of the high traffic between instances and incurred costs on traffic.
YES because, it's a recommended configuration to segregate traffic between App and DB instances to different subnets within the same Virtual Network.
YES because that's exactly why it is not recommended.
YES, YES, YES. Please find this notes in the microsoft article
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general
Another design that's not supported is the segregation of the SAP application layer and the DBMS layer into different Azure virtual networks that aren't peered with each other. We recommend that you segregate the SAP application layer and DBMS layer by using subnets within an Azure virtual network instead of by using different Azure virtual networks.
If you decide not to follow the recommendation and instead segregate the two layers into different virtual networks, the two virtual networks must be peered.
Be aware that network traffic between two peered Azure virtual networks is subject to transfer costs. Huge data volume that consists of many terabytes is exchanged between the SAP application layer and the DBMS layer. You can accumulate substantial costs if the SAP application layer and DBMS layer are segregated between two peered Azure virtual networks.
Y,Y,Y
The database VMs run in the same virtual network as the application layer, separated in a different subnet from the SAP application layer.
https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/dbms_guide_general
A design that is NOT supported is the segregation of the SAP application layer and the DBMS layer into different Azure virtual networks that are not peered with each other. It is recommended to segregate the SAP application layer and DBMS layer using subnets within an Azure virtual network instead of using different Azure virtual networks. If you decide not to follow the recommendation and instead segregate the two layers into different virtual network, the two virtual networks need to be peered. Be aware that network traffic between two peered Azure virtual networks are subject of transfer costs. With the huge data volume in many Terabytes exchanged between the SAP application layer and DBMS layer substantial costs can be accumulated if the SAP application layer and DBMS layer is segregated between two peered Azure virtual networks.
Source: SAP Note 2015553
NO YES YES.
A lot of the replies below are just very misguided sadly :(
Global VNet peering is for DR to live site. Within a deployment, APP and DB layers are within a VNet and different subnets.
https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/sap/sap-s4hana
Because of the Global Vnet Peering (peering two vents in two ) answer should be
NO,YES,YES
Segregating SAP application layer and DB layer into two Vnets in two different regions creates huge latency
Azure supports the following types of peering:
Virtual network peering: Connect virtual networks within the same Azure region.
Global virtual network peering: Connecting virtual networks across Azure regions.
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-peering-overview
Global vNet peering requires the use of network virtual appliances or vnet Gateways.
this is not supported as per this doc : https://docs.microsoft.com/en-us/learn/modules/plan-implement-sap-solutions/2-azure-vm-compute-network-storage-considerations-sap-workloads
" Keep in mind that configuring network virtual appliances in the communication path between the SAP application and the DBMS layer of an SAP NetWeaver-, Hybris-, or S/4HANA-based SAP system isn't supported. This restriction is for functionality and performance reasons. The communication path between the SAP application layer and the DBMS layer must be a direct one. "
Ans should be N Y Y
1) it is asked explicitly for Global not local. if it is local then Yes. if it is global ans should be n.
2) can be separated with subnet in with in same vlan.
3) yes, cost will increase if you separate them using two vnets (must be peered )
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.
Yogesh_g_w
Highly Voted 3 years, 9 months agoITDog99
10 months, 1 week agoSourabh1703
Highly Voted 3 years, 10 months agoAvanade2023
3 years, 8 months agomaybelline_ny
3 years, 9 months agoKumariswati
Most Recent 8 months, 1 week agoMadPanda
10 months, 3 weeks agomadgonc
1 year, 11 months agoashishsureka
2 years, 6 months agod0bermannn
2 years, 7 months agod0bermannn
2 years, 7 months agoLizzyOlivan
2 years, 10 months agod0bermannn
2 years, 6 months agosakibmas
2 years, 12 months agoJeb
3 years, 1 month agogills
3 years, 2 months agoAzure1971
3 years, 2 months agoAzure1971
3 years, 2 months agoShub94
3 years, 2 months agoNarenderSingh
3 years, 3 months agoimadedakir
3 years, 4 months agor05han
3 years, 4 months agoimadedakir
3 years, 4 months agoBhanuxyz
3 years, 5 months ago