Answer-first summary for fast verification
Answer: Include the forwarder agent in a DaemonSet deployment.
**Correct Answer: D** - **Option A (SSH to each node and run a script)** is not scalable. It requires manual intervention every time the cluster autoscales, adding operational overhead and potential for errors. - **Option B (StatefulSet deployment)** is unsuitable. StatefulSets are designed for pods requiring persistent storage across multiple zones, not for deploying agents like Splunk forwarder. - **Option C (Deployment Manager)** cannot be used to create Kubernetes deployments or apply configuration files, making it ineffective for this scenario. - **Option D (DaemonSet deployment)** is correct. DaemonSets ensure a pod runs on every node in the cluster, automatically scaling with the cluster. This method automates the installation and configuration of the Splunk forwarder agent on each node, minimizing operational overhead. References: - [StatefulSets in GKE](https://cloud.google.com/kubernetes-engine/docs/concepts/statefulset) - [Deployment Manager Fundamentals](https://cloud.google.com/deployment-manager/docs/fundamentals) - [DaemonSets in GKE](https://cloud.google.com/kubernetes-engine/docs/concepts/daemonset)
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your team utilizes Splunk for centralized logging, with numerous reports and dashboards based on Splunk logs. You aim to install Splunk forwarder on all nodes of your new Kubernetes Engine Autoscaled Cluster to forward logs to a centralized Splunk Server, minimizing operational overhead. What is the optimal method to install Splunk Forwarder on all cluster nodes?
A
SSH to each node and execute a script to install the forwarder agent.
B
Incorporate the forwarder agent in a StatefulSet deployment.
C
Utilize Deployment Manager to orchestrate the deployment of forwarder agents on all nodes.
D
Include the forwarder agent in a DaemonSet deployment.