Exam Associate Cloud Engineer topic 1 question 69 discussion

Correct Answer is (A): Adding an API as a type provider This page describes how to add an API to Google Cloud Deployment Manager as a type provider. To learn more about types and type providers, read the Types overview documentation. A type provider exposes all of the resources of a third-party API to Deployment Manager as base types that you can use in your configurations. These types must be directly served by a RESTful API that supports Create, Read, Update, and Delete (CRUD). If you want to use an API that is not automatically provided by Google with Deployment Manager, you must add the API as a type provider. https://cloud.google.com/deployment-manager/docs/configuration/type-providers/creating-type-provider

couldn't be more confusing

A is the correct , bcoz it help you contact directly to the gke cluster to create daemon

Should have been D

option A is the right answer because it lets you directly interact with the Kubernetes API to create the Daemonset using the same deployment Manager Deployment

I would say both Answer A and Answer D are valid solutions, and it depends on your preference and requirements. Answer A involves adding the cluster's API as a new Type Provider in Deployment Manager and using the new type to create the DaemonSet. This solution would allow you to create and manage the DaemonSet and the cluster in the same Deployment Manager deployment. Answer D involves adding a metadata block to the Deployment Manager deployment of the cluster, which will create the DaemonSet in the kube-system namespace of the cluster. This solution would allow you to create the DaemonSet in a simple way and avoid the need to create a new Type of Provider. In conclusion, I would choose Answer A to be considered the answer that uses the fewest possible services, as it only involves adding the cluster's API as a new Type Provider in Deployment Manager, which is a lightweight solution.

D. In the cluster's definition in Deployment Manager, add a metadata that has kube-system as key and the DaemonSet manifest as value. This approach involves adding the DaemonSet manifest directly as a metadata entry in the cluster's definition in Deployment Manager. When the cluster is created, the DaemonSet is automatically created in the kube-system namespace. This approach is the simplest and requires the fewest number of services. Option A is also a viable solution but requires more work to set up a Type Provider. Option B is not suitable because it involves a separate service (Runtime Configurator). Option C is also not recommended because it involves creating a Compute Engine instance and using kubectl to create the DaemonSet, which is more complicated and less efficient than the other options.

Option A is the right answer

Answer is A.

go with A as per ESP_SAP explanations..

Go for A

A is the correct answe, the API need to be added as a type provider

A should be correct one

https://medium.com/google-cloud/cloud-deployment-manager-kubernetes-2dd9b8124223

Correct Answer is (A)

A. Add the clusterג€™s API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.

dd the clusterג€™s API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.