A Cloud Engineer is establishing command-line administration for a newly deployed Google Kubernetes Engine (GKE) cluster named `analytics-cluster` in zone `us-central1-a`. The engineer also needs to configure node pools to host a stateful, non-fault-tolerant database workload. Which two actions should the engineer perform to fulfill these operational requirements? (Select TWO.)
- Run `gcloud container clusters get-credentials analytics-cluster --zone us-central1-a` to populate the local kubeconfig file with cluster endpoint and authentication details.Answer
- Provision a dedicated node pool using standard On-Demand Compute Engine VM instances for the database workload.Answer
- CExecute `gcloud config set container/cluster analytics-cluster` to generate client certificates and set up kubectl cluster context.
- DConfigure a Spot VM node pool for the database workload to minimize compute infrastructure costs.
Answer
The engineer must run `gcloud container clusters get-credentials analytics-cluster --zone us-central1-a` to configure local `kubectl` authentication, and provision standard On-Demand Compute Engine node pools for the stateful, non-fault-tolerant database workload.
To grant `kubectl` command-line access to a GKE cluster, administrators must fetch credentials via `gcloud container clusters get-credentials`, which updates the local `kubeconfig` file. Additionally, stateful and non-fault-tolerant workloads such as databases require persistent compute availability, making standard On-Demand node pools the correct architectural choice.
Step-by-Step Solution
Key Concept
GKE kubectl credential configuration and workload-to-node pool matching strategy