KCNA 無料問題集「Linux Foundation Kubernetes and Cloud Native Associate」

（A）The pod will be rescheduled to a different node in the cluster.

（B）The pod will be automatically scaled down.

（C）The pod will be marked as "unhealthy", but will continue to run.

（D）The pod will be automatically restarted.

（E）The pod will be terminated and removed from the cluster.

（A）Increased collaboration and knowledge sharing

（B）Stronger security due to centralized control

（C）Reduced development costs due to shared resources

（D）Improved maintainability and support

（E）Faster innovation and adoption of new technologies

（A）Use a StatefulSet to manage the deployment of the application.

（B）Implement a custom scaling logic that ensures state persistence during scaling events.

（C）Disable scaling for the application to maintain state consistency.

（D）Use a persistent volume claim (PVC) to store the application's state.

（E）Configure the HPA to scale up and down only when the application is idle.

（A）Deployment

（B）StatefulSet

（C）pod

（D）ReplicaSet

（E）Service

（A）Configure a Kubernetes Service to expose the Prometheus metrics to the HPA.

（B）Use the '-metrics-sources flag for the HPA command to specify the Prometheus endpoint.

（C）Use a custom Kubernetes controller that connects the HPA to Prometheus.

（D）Create a Kubernetes Custom Resource Definition (CRD) to define the Prometheus metric.

（E）Use the '-metrics' flag in the Deployment YAML file to link the HPA to Prometheus metrics.

（A）Provides a central point of control and management for the Kubernetes cluster.

（B）Schedules Pods to nodes based on resource availability and node affinity

（C）Enables communication between Pods and services within a Kubernetes cluster.

（D）Provides a secure and reliable connection between the Kubernetes control plane and nodes.

（E）Manages the lifecycle of Pods, ensuring that they are running as intended.

（A）The ArgoCD server is not running or is not properly configured.

（B）The ArgoCD application is not properly configured to watch the specific Git repository for changes.

（C）The deployment configuration in the Git repository is invalid or does not match the desired state.

（D）The Git repository is not accessible by ArgoCD.

（E）The Kubernetes cluster is not accessible by ArgoC

（A）kubectl delete deployment my-app

（B）kubectl scale deployment my-app -replicas=0

（C）kubectl apply -f deployment.yaml

（D）kubectl rollout restart deployment my-app

（E）kubectl set image deployment/my-app my-app-container=my-app:v2

（A）Latency and throughput of requests to the Kubernetes API server.

（B）Number of pods running in each namespace.

（C）Number of active Kubernetes controllers (e.g., Deployment, ReplicaSet).

（D）Number of failed deployments and pod restarts.

（E）Total CPU and memory usage across all nodes in the cluster.

（A）ArgoCD is a tool for managing Kubernetes secrets and sensitive data.

（B）ArgoCD is a continuous integration and continuous delivery (CIICD) tool for building and testing applications.

（C）ArgoCD is a container orchestration platform for managing Kubernetes deployments.

（D）ArgoCD is a cloud-native storage solution for storing Kubernetes configurations.

（E）ArgoCD is a GitOps engine that synchronizes your Kubernetes cluster with your Git repository, ensuring your desired state is maintained.