MENU
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?
Suggested Answer: A
Get Premium Associate Cloud Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
40 comments · newest first
ST
Stacey
11 months ago
I think B is the best option for flexibility in deployments.
CA
Carolynn
11 months ago
Wait, can you really do it with D? That sounds too simple!
PA
Pa
11 months ago
C sounds like overkill for just a DaemonSet.
JE
Jerry
11 months ago
I disagree, B seems more straightforward for managing configs.
FL
Fletcher
12 months ago
A is the way to go! Using Type Providers makes it cleaner.
SH
Shawnee
12 months ago
Option D seems interesting, but I can't recall if adding metadata like that is the right approach for Deployment Manager.
ME
Merlyn
1 year 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.
FR
France
1 year 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.
JO
Jolene
1 year ago
I think option A sounds familiar, but I'm not entirely sure how to add the API as a Type Provider.
GE
Gertude
1 year 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.
PH
Phuong
1 year 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.
EA
Earleen
1 year 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.
MA
Marisha
1 year ago
This looks like a tricky one. I'll need to think through the different options carefully to determine the most efficient solution.
LY
Lyndia
1 year 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.
AR
Ardella
1 year ago
- JaneDoe
RO
Roosevelt
1 year ago
This seems straightforward. I'll focus on the instructions to change the line spacing to 1.15 lines for the entire document.
KA
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?
MO
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.
DO
Dorian
1 year ago
C) With Deployment Manager, create a Compute Engine instance with a startup script that uses kubectl to create the DaemonSet.
KE
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?
AL
Alishia
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
DE
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.
DE
Devon
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
DO
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.
AL
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.
BR
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.
GO
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.
LE
Leonor
1 year ago
B) Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.
DO
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.
FA
Fausto
2 years 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.
BA
Barrett
1 year ago
Yeah, using metadata in the cluster's definition seems like the easiest way to go.
LO
Lon
1 year ago
I think option D is the simplest solution.
AN
Andrew
2 years 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.
RA
Raymon
2 years 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.
VA
Vanda
2 years 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.
JE
Jesusita
1 year ago
Let's go with Option B then.
WI
Wilda
1 year ago
I agree, it's a straightforward approach to create the DaemonSet.
LA
Laurel
1 year ago
Yeah, using the Runtime Configurator seems like the simplest solution.
BE
Benton
2 years ago
I think Option B is the best choice.
AZ
Azalee
2 years 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.