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

（A）HorizontalPodAutoscaler

（B）Deployment

（C）PodDisruptionBudget

（D）NodeSelector

（E）Service

（A）Self-healing

（B）Pod Disruption Budgets

（C）Rolling updates

（D）Horizontal Pod Autoscaling

（E）Node affinity

（A）Deployments are used for stateless applications, while StatefulSets are used for stateful applications that require persistent storage and unique identities.

（B）Deployments are used for managing the lifecycle of a single Pod, while StatefulSets manage multiple Pods.

（C）Deployments are responsible for scheduling Pods, while StatefulSets manage the lifecycle of Services.

（D）Deployments are used for deploying and managing stateless applications, while StatefulSets are used for deploying and managing stateful applications.

（E）Deployments handle rolling updates, while StatefulSets only support manual updates.

（A）Use AWS Lambda's built-in S3 client to read data from the bucket.

（B）Download the entire S3 object into the Lambda function's memory.

（C）Stream data directly from S3 to the Lambda function using the S3 API.

（D）Utilize AWS Kinesis to stream data from S3 to the Lambda function.

（E）Use the AWS SDK for Python (Bot03) to access S3 objects directly.

（A）Google Cloud Functions

（B）Google Cloud Storage

（C）Google App Engine

（D）Google Kubernetes Engine (GKE)

（E）Google Cloud SQL

（A）Namespaces

（B）ConfigMaps

（C）Services

（D）Secrets

（E）Deployments

（A）Use serverless frameworks like AWS Serverless Application Model (SAM) to manage Lambda deployments.

（B）Configure Lambda functions to use a larger memory allocation.

（C）Enable concurrency settings for Lambda functions to allow multiple invocations simultaneously.

（D）Utilize AWS Elastic Beanstalk to auto-scale Lambda functions based on workload.

（E）Implement a message queue in front of Lambda functions to buffer incoming requests.

（A）Use a horizontal pod autoscaler (HPA) with metrics based on CPU and memory utilization.

（B）Manually scale the deployment up during traffic spikes and down afterward.

（C）Utilize serverless functions to handle the peak traffic load, automatically scaling as needed.

（D）Configure a resource quota for the web application's namespace to limit its resource usage.

（E）Implement a caching layer in front of the web application to reduce the load on the backend servers.

（A）PersistentVolumeClaim

（B）Namespace

（C）Secret

（D）ConfigMap

（E）Service

（A）Pay-per-use pricing model.

（B）Pre-provisioned and managed servers-

（C）Automatic scaling based on workload demand

（D）Focus on business logic rather than infrastructure management

（E）Event-driven execution model.