Exam Professional Cloud Architect topic 1 question 31 discussion

it should be A .. helm is needed for "Deploy application bundles using dynamic templates" Load Balancing should be part of GKE Already

D. Google Kubernetes Engine, Jenkins, and Cloud Load Balancing

A is the only answer that contains all items based on open-source technology for cloud portability.

For networking part, D is required

A is correct

Option A (Google Kubernetes Engine, Jenkins, and Helm): This option explicitly includes Helm, which is used for templated deployments. However, since GKE itself supports Helm, this option may be seen as redundant in the context of the requirements. Option D (Google Kubernetes Engine, Jenkins, and Cloud Load Balancing): This option includes Jenkins for continuous delivery and Cloud Load Balancing for routing traffic. While it doesn't mention Helm, the dynamic template deployment can still be managed through Jenkins scripts or other CI/CD tools.

D: load balancing is needed for this requirement: 6. Route network traffic to specific services based on URL

A & D are both right Why D Might Still Be Preferred: While A is a valid choice, D (Google Kubernetes Engine, Jenkins, and Cloud Load Balancing) might be preferred for the following reasons: Cloud Load Balancing provides a more feature-rich, fully managed solution for routing traffic across multiple regions and services, including advanced load balancing, SSL termination, and support for more sophisticated network traffic management. It integrates well with GKE and offers additional scalability and flexibility that might be important as your system grows

1. Open-source technology: Kubernetes Engine, Jenkins, and Helm. 2. Dynamically scale compute capacity: Kubernetes Engine provides autoscaling to adjust the number of nodes based on demand. 3. Support continuous software delivery: Jenkins enables CI/CD pipelines for automated building, testing, and deployment of applications. 4. Run multiple segregated copies: Kubernetes Engine allows deploying multiple instances of the application in isolated environments (namespaces) within the same cluster. 5. Deploy application bundles using dynamic templates: Helm uses charts (templates) to define, install, and upgrade Kubernetes applications. 6. Route network traffic based on URL: Kubernetes Engine's service objects and ingress controllers can route traffic to specific services based on URLs and other criteria.

Based on: "Be based on open-source technology for cloud portability", I go for A, because it is more portable, as compare to D.

Choose A

Yes, Kubernetes can route network traffic to specific services based on URL using Ingress and Ingress controllers Answer is A

Load Balancer is required as per point 6. Jenkins satisfies point 3. D is correct

D is correct

Option A (GKE, Jenkins, Helm) meets most requirements except for explicit URL-based routing, though Kubernetes Ingress (which can be managed through Helm charts) implicitly covers this. Option D (GKE, Jenkins, Cloud Load Balancing) directly meets every requirement, including URL-based routing without needing to infer capabilities or integrate additional tools beyond the scope of what's listed. Jenkins supports continuous delivery, GKE supports dynamic scaling, segregated application stacks, and cloud portability. Cloud Load Balancing directly addresses the URL-based routing requirement.

D is OK

1. Be based on open-source technology for cloud portability: GKE 2. Dynamically scale compute capacity based on demand: GKE 3. Support continuous software delivery: Jenkins 4. Run multiple segregated copies of the same application stack: GKE 5. Deploy application bundles using dynamic templates -> Jenkins 6. Route network traffic to specific services based on URL -> Only HTTPs load balancer can meet this requirement: Next best is Cloud balancing (that can be either Network or HTTPs), So D makes sense to me.