Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Associate Cloud Engineer Exam - Topic 4 Question 86 Discussion

You are using Deployment Manager to create a Google Kubernetes Engine cluster. Using the same Deployment Manager deployment, you also want to create a DaemonSet in the kube-system namespace of the cluster. You want a solution that uses the fewest possible services. What should you do?
A) Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
C) With Deployment Manager, create a Compute Engine instance with a startup script that uses kubectl to create the DaemonSet.
D) In the cluster's definition in Deployment Manager, add a metadata that has kube-system as key and the DaemonSet manifest as value.

Google Associate Cloud Engineer Exam - Topic 4 Question 86 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 86
Topic #: 4
[All Associate Cloud Engineer Questions]

You are using Deployment Manager to create a Google Kubernetes Engine cluster. Using the same Deployment Manager deployment, you also want to create a DaemonSet in the kube-system namespace of the cluster. You want a solution that uses the fewest possible services. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

A managed instance group (MIG) is a group of identical virtual machines (VMs) that you can manage as a single entity. You can use a MIG to deploy and maintain a stateless application that runs directly on VMs. A MIG can automatically scale the number of VMs based on the load or a schedule. A MIG can also automatically heal the VMs if they become unhealthy or unavailable. A MIG is suitable for applications that need to run on VMs rather than containers or serverless platforms.

B is incorrect because Kubernetes Engine is a managed service for running containerized applications on a cluster of nodes. It is not necessary to use Kubernetes Engine if the application does not use containers and can run directly on VMs.

C is incorrect because Cloud Functions is a serverless platform for running event-driven code in response to triggers. It is not suitable for applications that need to run continuously and handle HTTP requests.

D is incorrect because Cloud Run is a serverless platform for running stateless containerized applications. It is not suitable for applications that do not use containers and can run directly on VMs.


Managed instance groups documentation

Choosing a compute option for Google Cloud

by Alfreda at Jul 01, 2024, 08:36 AM

Limited Time Offer

25%

Off

Get Premium Associate Cloud Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Stacey
9 months ago
I think B is the best option for flexibility in deployments.
upvoted 0 times
...
Carolynn
9 months ago
Wait, can you really do it with D? That sounds too simple!
upvoted 0 times
...
Pa
10 months ago
C sounds like overkill for just a DaemonSet.
upvoted 0 times
...
Jerry
10 months ago
I disagree, B seems more straightforward for managing configs.
upvoted 0 times
...
Fletcher
10 months ago
A is the way to go! Using Type Providers makes it cleaner.
upvoted 0 times
...
Shawnee
10 months ago
Option D seems interesting, but I can't recall if adding metadata like that is the right approach for Deployment Manager.
upvoted 0 times
...
Merlyn
11 months ago
I feel like creating a Compute Engine instance with a startup script, like in option C, is a bit overkill for just a DaemonSet.
upvoted 0 times
...
France
11 months ago
I remember practicing with the Runtime Configurator, so option B might be the way to go, but I’m not confident about the specifics.
upvoted 0 times
...
Jolene
11 months ago
I think option A sounds familiar, but I'm not entirely sure how to add the API as a Type Provider.
upvoted 0 times
...
Gertude
11 months ago
This is straightforward. I'd go with option B and use the Runtime Configurator to create the DaemonSet. That way, I can keep everything in Deployment Manager and avoid having to use additional services.
upvoted 0 times
...
Phuong
11 months ago
Okay, I think I've got this. Based on the question, it seems like the best approach would be to use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition. That way, I can manage the entire deployment through Deployment Manager.
upvoted 0 times
...
Earleen
11 months ago
Hmm, I'm a bit confused by the question. I'm not sure if I fully understand the relationship between Deployment Manager and Kubernetes. I'll need to review my notes on these services.
upvoted 0 times
...
Marisha
11 months ago
This looks like a tricky one. I'll need to think through the different options carefully to determine the most efficient solution.
upvoted 0 times
...
Lyndia
11 months ago
I'm a bit confused by this question. I'm not familiar with all the features of ECE, so I'll have to make an educated guess here.
upvoted 0 times
...
Ardella
11 months ago
- JaneDoe
upvoted 0 times
...
Roosevelt
11 months ago
This seems straightforward. I'll focus on the instructions to change the line spacing to 1.15 lines for the entire document.
upvoted 0 times
...
Karan
1 year ago
I think I'll just write a Python script that deploys the DaemonSet, the cluster, and my entire infrastructure. Who needs Deployment Manager when you have spaghetti code?
upvoted 0 times
Mozell
1 year ago
D) In the cluster's definition in Deployment Manager, add a metadata that has kube-system as key and the DaemonSet manifest as value.
upvoted 0 times
...
Dorian
1 year ago
C) With Deployment Manager, create a Compute Engine instance with a startup script that uses kubectl to create the DaemonSet.
upvoted 0 times
...
Kenda
1 year ago
I think I'll just write a Python script that deploys the DaemonSet, the cluster, and my entire infrastructure. Who needs Deployment Manager when you have spaghetti code?
upvoted 0 times
...
Alishia
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
upvoted 0 times
...
Deandrea
1 year ago
A) Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.
upvoted 0 times
...
Devon
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
upvoted 0 times
...
Dorethea
1 year ago
A) Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.
upvoted 0 times
...
...
Alaine
1 year ago
Option D seems the most elegant to me. Keeping everything in the cluster's definition just makes sense. Plus, it avoids any extra services or resources.
upvoted 0 times
...
Brunilda
1 year ago
Creating a Compute Engine instance with a startup script? That's a creative solution, but it also feels a bit convoluted. I think I'll stick with the Deployment Manager options.
upvoted 0 times
Goldie
1 year ago
Creating a Compute Engine instance with a startup script? That's a creative solution, but it also feels a bit convoluted. I think I'll stick with the Deployment Manager options.
upvoted 0 times
...
Leonor
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
upvoted 0 times
...
Dorathy
1 year ago
A) Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.
upvoted 0 times
...
...
Fausto
1 year ago
Hmm, I'm not sure about adding the cluster's API as a new Type Provider. Feels a bit overkill for just a DaemonSet. I'm leaning towards option D.
upvoted 0 times
Barrett
1 year ago
Yeah, using metadata in the cluster's definition seems like the easiest way to go.
upvoted 0 times
...
Lon
1 year ago
I think option D is the simplest solution.
upvoted 0 times
...
...
Andrew
1 year ago
I'm not sure, but I think B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition could also be a valid option.
upvoted 0 times
...
Raymon
1 year ago
I disagree, I believe the answer is C) With Deployment Manager, create a Compute Engine instance with a startup script that uses kubectl to create the DaemonSet.
upvoted 0 times
...
Vanda
1 year ago
Option B sounds like the way to go. I like how it uses the Runtime Configurator to create the DaemonSet - seems the most straightforward approach.
upvoted 0 times
Jesusita
1 year ago
Let's go with Option B then.
upvoted 0 times
...
Wilda
1 year ago
I agree, it's a straightforward approach to create the DaemonSet.
upvoted 0 times
...
Laurel
1 year ago
Yeah, using the Runtime Configurator seems like the simplest solution.
upvoted 0 times
...
Benton
1 year ago
I think Option B is the best choice.
upvoted 0 times
...
...
Azalee
1 year ago
I think the answer is A) Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.
upvoted 0 times
...

Save Cancel