Google Cloud Certified Associate Cloud Engineer Practice

What's the easiest way to expose a workload in a scenario where a deployment is already visible under Workloads in the console?

1. Create a new Service that points to the existing deployment.

2. Create a new DaemonSet.

3. Create a Global Load Balancer that points to the pod in the deployment.

4. Create a Static IP Address Resource for the Deployment.

The correct answer is: Create a new Service that points to the existing deployment.

When creating a new Service, you can specify the existing deployment as its target. This will enable the use of the service's DNS name when referring to the pods in the deployment. B Creating a DaemonSet would result in a pod being created on each node in the cluster, which would not be a suitable solution if you only want one instance of your workload deployed. C: Creating a Global Load Balancer would attempt to balance traffic across all nodes in the cluster hosting the pods in the deployment, which is unnecessary and potentially wasteful if there is only one pod in the deployment. D: Creating a Static IP Address Resource would not expose the workload, but rather assign a static IP to the deployment itself.