Jawaban Getting Started with Google Kubernetes Engine II Kubernetes Architecture

 

Kubernetes Concepts

1.What is the difference between a pod and a container?

A pod contains one or more containers.

A container contains one or more pods.

Pods and containers are two names for the same thing.


Google Kubernetes Engine Concepts

1.In GKE clusters, how are nodes provisioned?

As Compute Engine virtual machines

As abstract parts of the GKE service that are not exposed to Google Cloud customers



2.What is the purpose of configuring a regional cluster in GKE?

To allow applications running in the cluster to withstand the loss of a zone

To ensure that the cluster's workloads are isolated from the public Internet


3.In GKE, how are control planes provisioned?

As Compute Engine virtual machines

As abstract parts of the GKE service that are not exposed to Google Cloud customers

 

Kubernetes Object Management


1. What is the purpose of the Deployment object?

To ensure that a defined set of Pods is running at any given time.

To launch one or more Pods on a time-based schedule.

To launch one or more Pods and ensure that a specified number of them successfully run to completion and exit

 

2. What are Kubernetes namespaces useful for? Choose all that are correct (2 correct answers).

Namespaces let you implement resource quotas across your cluster.

Namespaces make resources more secure,

Namespaces partition Linux kernel resources.

Namespaces allow you to use object names that would otherwise be duplicates of one another.

3.In a manifest file for a Pod, in which field do you define a container image for the Pod?

spec

metadata

kind

apiVersion


Kubernetes Controller Objects

1.What is the purpose of a Service? Choose all that are true (2 correct answers)

To allow you to choose how Pods are exposed

To provide a way to inspect and diagnose code running in a Pod

To provide a load-balancing network endpoint for Pods

To allow you to put constraints on Pods' resource consumption


2.If you are deploying applications in your Pods that need persistent storage, which controller type should you use?

Deployment

ReplicaSet

StatefulSet

DaemonSet 


Kubernetes Architecture

1.You need to ensure that the production applications running on your Kubernetes cluster are not impacted by test and staging deployments. Which features should you implement and configure to ensure that the resources for your production applications can be prioritized?

Configure labels for Test, Staging and Production and configure specific Kubernetes resource quotas for the Production Namespace.

 

Configure Namespaces for Test, Staging and Production and configure specific Kubernetes resource quotas for the test and staging Namespaces.

Configure Namespaces for Test, Staging and Production and configure specific Kubernetes resource quotas for the Production Namespace.

Configure resource requests for Test, Staging and Production and configure specific Kubernetes resource quotas for the Production Namespace.

That is correct. Resource quotas are used to limit usage in specific Namespaces, and do not need to be configured for all Namespaces, only those you need to limit.


2.You want to deploy multiple copies of your application, so that you can load balance traffic across them. How should you deploy this application's Pods to the production Namespace in your cluster?

Create a Service manifest for the LoadBalancer that specifies the number of replicas you want to run.
check
Create a Deployment manifest that specifies the number of replicas that you want to run.

Create separate named Pod manifests for each instance of the application and deploy as many as you need.

Deploy the Pod manifest multiple times until you have achieved the number of replicas required.

3.Which Kubernetes component does the kubectl command connect to in order to carry out operations on a cluster?

kube-controller-manager

kube-apiserver

kube-dns

kube-scheduler


check
4.You have deployed a new Google Kubernetes Engine regional cluster with four machines in the default pool for the first zone and left the number of zones at the default. How many Compute Engine machines are deployed and billed against your account?

Sixteen. (Four nodes are deployed in primary and secondary zones in two regions, for a total of 4 zones and 16 nodes. A control plane node is deployed in each zone but it is not billed to your account.)

Ten. (Four nodes are deployed in the first zone and three nodes are deployed in two other zones because you selected the defaults.)

Twelve. (Four nodes are deployed in each of three zones. A control plane node is deployed in each zone which is indirectly billed against your account through the cluster management fee.)

Fifteen. (Four nodes and a single control plane are deployed to each of the three zones. A control plane node is deployed in each zone and it is billed against your account.)

That is correct. GKE Regional clusters are deployed across multiple zones in a single region. Google also deploys GKE control plane nodes in each zone.

5.When configuring storage for stateful applications, what steps must you take to provide file system storage inside your containers for data from your applications that will not be lost or deleted if your Pods fail or are deleted for any reason?

You must create Volumes using local Storage on the Nodes and mount the Volumes inside your containers to provide durable storage.                                                                                                   
You must create Volumes using network based storage to provide durable storage remote to the Pods and specify these in the Pods.

You must mount NFS Volumes on each container in the Pod that requires durable storage.

You must export the data from your applications to a remote service that preserves your data.

6.You are designing an application, and you want to ensure that the containers are located as close to each other as possible, in order to minimize latency. Which design decision helps meet this requirement?

Give the containers the same labels.
check
Place the containers in the same Pod.

Place the containers in the same cluster.

Place the containers in the same Namespace.

 

Posting Komentar

Lebih baru Lebih lama