Exam Professional Cloud Architect topic 1 question 104 discussion

Correct Ans : D Since the Traffic is TCP, Ans A & C gets eliminated as HTTPS load balance is not supported. B - File storage system is Cloud Firestore which do not give full control, hence eliminated. D - Unmanaged instance group with network load balance with regional persistent disk for storage gives full control which is required for the migration.

Ans ) D , unmanaged instance group as application does not support horizontal scaling and network load balancer as no mention of http traffic .

In Unmanaged Instance Group instances cannot be in different zones. I think that correct is D but maybe a mistake in the question.

Why not a B? Because the application doesn't support for horizonal scale. I chose D.

D is corrrect TCP load balancer plus UNMANAGED

must be unmanaged

Since the application does not support horizontal scaling, a managed instance group is not required. Instead, an unmanaged instance group can be used to ensure that the application runs on multiple instances in different zones for high availability. The network load balancer is designed to handle TCP and UDP traffic The HTTP(S) load balancer is designed specifically for HTTP and HTTPS traffic.

An unmanaged instance group allows you to create and manage a group of Compute Engine instances manually, rather than using an autoscaling solution like a managed instance group. This is appropriate for an application that does not support horizontal scaling, as you can manually create and manage the number of instances needed to meet the traffic demands. To ensure high availability and minimize downtime, you should deploy the instances in different zones and use a regional persistent disk to store the application's data. This will ensure that the application is still available even if one of the instances or a zone experiences an outage. A network load balancer should be used in front of the instances to distribute traffic to the instances. A network load balancer is a highly available and scalable load balancing solution that operates at the network layer and can handle high volumes of traffic. It can also balance traffic across multiple zones to ensure that the application is always available to users.

Regional Persistent Disk, as App requires full control of filesystem data without concurrent access (block storage vs. file storage (NAS). https://cloud.google.com/compute/docs/instance-groups https://cloud.google.com/load-balancing/docs/choosing-load-balancer

Option A & B eliminated because we cannot use managed instance group since the app does not support Horizontal scaling Option C > HTTP load balancer is Layer 7 & application is receiving traffic via TCP Option D > is best answer because we are using Network load balancer Layer 4 which meets the condition "application receives traffic via TCP"

Checking the comparative analysis of storage options, we can see that Filestore is not suitable for the workload, hence A and B are out. C is out because it restricts to HTTP traffic. Answer is D

D is ok

D is not possibile you cannot create a regional unmanaged instance group. https://cloud.google.com/compute/docs/instance-groups/creating-groups-of-unmanaged-instances

D. Use an unmanaged instance group with an active and standby instance in different zones, use a regional persistent disk, and use a network load balancer in front of the instances. D is the only option as the application does not support horizontal scaling (no MIG), it needs full control (no filestore) and has TCP traffic (no HTTP LB).

D is more appropriate solution ---In the ques. it is mentioned done not support horizontal scaling --> hence Unmanaged Instance , and traffic is TCP --- hence N/W Load balancer

does not support horizontal scaling so MIG not needed. TCP traffic so NW LB is ok

concurrent access causes corruption - it can not be a managed group