This one is quite ambiguous, because we don't know much about the VoIP app.
A: No, VoIP is unlikely to use HTTP(S)
B: Likely - this is the only Internet-facing UDP option. VoIP apps tend to use UDP but we don't know that for sure.
C: No, has to be Internet facing
D: Maybe, if it does use TCP or SSL
A Network Load Balancer is designed for handling low-level TCP/UDP traffic and can distribute traffic efficiently based on IP protocol and port numbers. VoIP applications typically rely on UDP traffic and need to handle high-throughput and low-latency traffic, which makes the Network Load Balancer the most suitable for this use cas
TCP/SSL Proxy Load Balancing is a type of load balancing that is designed for applications that use the TCP protocol and require SSL/TLS encryption. This type of load balancer is ideal for internet-facing applications, such as VOIP applications, that require high levels of security and performance.
The other options are incorrect because:
A. HTTP(s) load balancer is designed for applications that use the HTTP or HTTPS protocol.
B. Network load balancer is designed for applications that use the TCP or UDP protocol.
C. Internal TCP/UDP load balancer is designed for applications that use the TCP or UDP protocol and are not exposed to the internet.
Therefore, the best option for load balancing an internet-facing, standard VOIP application is a TCP/SSL proxy load balancer.
For a standard voice-over-IP (VOIP) application, where real-time communication is typically conducted over UDP (User Datagram Protocol), the appropriate choice is:
B. Network load balancer
The Network Load Balancer in Google Cloud is designed to handle both TCP and UDP traffic. It is a Layer 4 (transport layer) load balancer that works with protocols beyond just HTTP(S). Since VOIP applications often use UDP for real-time communication, the Network Load Balancer is well-suited to distribute UDP traffic efficiently.
VOIP makes use of both TCP and UDP. The option D does not specify UDP ...so we cant use TCP/SSL proxy load balancer. Hence answer is B - Network load balancer
The appropriate type of load balancer for an internet-facing, standard voice-over-IP (VOIP) application is a TCP/SSL proxy load balancer (option D). TCP/SSL proxy load balancer terminates SSL traffic and balances TCP traffic, which is suitable for VOIP application traffic.
Option C (Internal TCP/UDP load balancer) is designed to distribute internal traffic within a single VPC network or between two peered VPC networks, and it doesn't provide internet-facing access to your application. Therefore, it is not the suitable choice for an internet-facing VOIP application.
Option B (Network load balancer) is designed to handle traffic at the transport layer (Layer 4) and can handle TCP/UDP traffic. However, it is a regional load balancer and does not provide global access, which is typically required for an internet-facing application.
Therefore, neither option C nor B is the best choice for an internet-facing VOIP application. Option D (TCP/SSL proxy load balancer) is more suitable for handling VOIP traffic.
Answer: B. Network load balancer.
Since the application is a voice-over-IP (VOIP) application, it is likely that it is using the TCP/UDP protocols. Also, since the application is internet-facing, a global load balancer is needed. Therefore, the appropriate type of load balancer to use is the External TCP/UDP Network Load Balancer.
IMP - there are two answers: B&C... We don't know the actually design...but we know VOIP is best effort and is UDP....
Internal TCP/UDP Load Balancing distributes traffic among internal virtual machine (VM) instances IN the same region in a Virtual Private Cloud (VPC) network. It enables you to run and scale your services behind an INTERNAL IP address that is accessible ONLY to systems in the same VPC network or systems connected to your VPC network....
With that said - a Cloud Router is needed to connect from the Internet to hit the ILB...BUT a Global LB is need to distribute the traffic correctly so a NetworkLB is required. The design should be a Hub-n-Spoke or a Shared VPC with a Service VPC to hold the Cloud router and Network LB....
I will go with Answer b for now as in said INTERNET FACING VOIP Application.
Thoughts?
https://cloud.google.com/load-balancing/docs/choosing-load-balancer
External facing is internet facing . Looking at the flow chart via the url above and knowing VOIP are usually USP based, I would opt for external network loadbalancer
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.
mozammil89
Highly Voted 4 years, 7 months agoarchitect
Highly Voted 4 years, 4 months agoJohnnyBG
3 years, 3 months agosaraali
Most Recent 2 months, 2 weeks agothewalker
6 months, 1 week agoirmingard_examtopics
7 months, 1 week agoxhilmi
10 months, 2 weeks agodidek1986
1 year, 2 months agogcpengineer
1 year, 2 months agogcpengineer
1 year, 2 months agoHetavi
1 year, 5 months agoKomal697
1 year, 7 months agoKomal697
1 year, 7 months agoBen756
1 year, 7 months agogcpengineer
1 year, 2 months agoBenMS
10 months, 1 week agopk349
1 year, 9 months agokapara
2 years, 4 months agokumarp6
2 years, 10 months agoclooudy
2 years, 9 months agogcpengineer
1 year, 2 months agodesertlotus1211
2 years, 10 months agodesertlotus1211
2 years, 10 months agoTejtej
2 years, 10 months ago