Q: 9
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?
Options
Discussion
B or C? Type Provider in A looks like a trap because it could count as another service. Not totally sure though.
Its C, since spinning up a Compute Engine instance and running kubectl seems simpler to me.
B not C
A is correct - using Deployment Manager plus a Type Provider just extends DM rather than spinning up something like Compute Engine (which C does). This way, you keep it to the minimum in terms of GCP-managed services. Pretty sure that's what Google expects here, but open to other views.
Probably A, Type Provider isn't a new GCP service here, unlike Compute Engine in C.
If a Type Provider is considered its own extra service beyond core Deployment Manager, does that make option C (Compute Engine + kubectl) actually use fewer services technically? The definition seems kind of fuzzy here.
A , using the Type Provider fits the scenario with no extra GCP services involved.
A , unless the custom Type Provider is counted as a separate service then maybe it's not the fewest.
Had something like this in a mock, pretty sure it's A.
I was thinking C too, since using a startup script with kubectl feels like it keeps things simple and avoids extra GCP setup. You just spin up an instance, run the manifest, done. Maybe it needs more ops overhead, but fewer GCP services involved I think. Correct me if I'm missing something.
Be respectful. No spam.