Exam Professional Cloud Architect All QuestionsBrowse all questions from this exam
Go to Exam
Question 31

A development manager is building a new application. He asks you to review his requirements and identify what cloud technologies he can use to meet them. The application must:

1. Be based on open-source technology for cloud portability

2. Dynamically scale compute capacity based on demand

3. Support continuous software delivery

4. Run multiple segregated copies of the same application stack

5. Deploy application bundles using dynamic templates

6. Route network traffic to specific services based on URL

Which combination of technologies will meet all of his requirements?

    Correct Answer: A

    D

    Jenkins is an open-source automation server that lets you flexibly orchestrate your build, test, and deployment pipelines. Kubernetes Engine is a hosted version of

    Kubernetes, a powerful cluster manager and orchestration system for containers.

    When you need to set up a continuous delivery (CD) pipeline, deploying Jenkins on Kubernetes Engine provides important benefits over a standard VM-based deployment

    Incorrect Answers:

    A: Helm is a tool for managing Kubernetes charts. Charts are packages of pre-configured Kubernetes resources.

    Use Helm to:

    Find and use popular software packaged as Kubernetes charts

    ✑ Share your own applications as Kubernetes charts

    ✑ Create reproducible builds of your Kubernetes applications

    ✑ Intelligently manage your Kubernetes manifest files

    ✑ Manage releases of Helm packages

    Reference:

    https://cloud.google.com/solutions/jenkins-on-kubernetes-engine

Discussion
rsamantOption: A

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

poseidon24

Not for "based on URL", that is the difference.

ashish_t

https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer#optional_serving_multiple_applications_on_a_load_balancer As per the above document and given example of "fanout-ingress.yaml" in above document and also in GKE sample repository below https://github.com/GoogleCloudPlatform/kubernetes-engine-samples/tree/master/load-balancing it's clear that GKE LB can handle "6. Route network traffic to specific services based on URL" So NO need for Cloud Load balancing. Helm satisfy "5. Deploy application bundles using dynamic templates" and no other option satisfies this point #5. So correct answer should be: A

raf2121

Kubernetes Engine offers integrated support for two types of Cloud Load Balancing (Ingress and External Network Load Balancing) , hence Option A Reference : https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer

AzureDP900

A should be fine

Prakzz

Load balancing is not a part of GKE untill it's created explicitly

victory108Option: D

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

ashishdwi007Option: D

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.

kahinahOption: D

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.

Sephethus

Except none of that meets the needs for deployment templates.

Ric350

My point exactly and my response to Chris_21. By process of elimination, you need Helm for the dynamic templates and you need Jenkins. Thus, you have to assume the application is internally facing and the ingress controllers will handle the traffic just fine.

MMuzammilOption: D

I thought that answer A was correct but after researching HELM I think now the option D is correct. Helm is not a cloud service on its own, and it is not built into Google Kubernetes Engine (GKE). Helm is an open-source package manager for Kubernetes that simplifies the deployment and management of applications on Kubernetes clusters. Here's a brief overview: Helm: Helm allows you to define, install, and upgrade even the most complex Kubernetes applications using packages called charts. A Helm chart includes pre-configured Kubernetes resources that define the structure of an application. Helm provides a convenient way to package, version, and deploy applications on Kubernetes.

Sephethus

A is the real-world answer, D is the "Google (TM)" answer I think. It's obnoxious how bad these questions are.

RKS_2021Option: D

K8s, Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software. and LB for traffic forwarding.

Chris_21Option: D

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

Ric350

Helm is needed for the dynamic templates requirement. The question is vague in whether the application is internally or externally facing which would clarify things a lot more for us. However, in its ambiguity option A has the techonologies neede to the requirments and thus deduce or infer that the application is internally facing and the ingress controllers will handle the routing of traffic. It's ambiguous on purpose which I hate in these exams. More of a test of how well we can read and interpret the questions vs our knowledge of material.

RehamssOption: D

D is correct

VidhyaBupeshOption: D

D is OK

kip21Option: D

D - Correct

adoytOption: A

Kubernetes natively supports routing to different services based on URLs via the ingress gateway regardless of wether a LB is used...

truepc

can you share full questions please <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="d4a3b5b8b1b1b0fab5b8aebbb9bba694b3b9b5bdb8fab7bbb9">[email protected]</a>

simiramis221Option: A

The correct answer is A, you can route network traffic to specific services based on URL using Google Kubernetes Engine (GKE) using Ingress

_kartik_rajOption: D

Correct should be D, Focus on this part of the question "what cloud technologies he can use to meet them", And Now coming to options ,B,C are self explanatory now coming to A Because Helm is not a Cloud Technology first, its just a package Manager for Kubernetes, and Even if you say Loadbalncing is part of GKE , actually whatever ingress you create for path based , It does create a load Balancer , and ultimately LOad Balancer is Definitely important, now coming to Templating I Feel there can be many tools we can use ex: Kustomize can be one of them but that is completly something User can decide and even create some customised way to templatize the deployment using YAML or shell or any other language .

Sephethus

I hate tests and this question is why I hate them. There is too much confusion in the question. I would say A is the real world answer, D is the Google (tm) answer.

Arun_m_123Option: D

Correct answer is D - Don't get confused with this option "Deploy application bundles using dynamic templates". In this option, they have mentioned as "Deploy applications". In GKE app deployment, can be configured using YAML files. Helm is not a highly preferred tool and that won't be a recommedation from Google. Answer is D

AdityaGuptaOption: D

Dynamic bundling - GKE CI/ CD - Jenkins Routing based on URL - Cloud B

theBestStudentOption: A

Continuous Delivery ----> ci-cd pipelines --->Jenkins

kenithyangOption: A

A is correct