Updated Jun-2024 Pass C_KYMD_01 Exam - Real Practice Test Questions
Download Free SAP C_KYMD_01 Real Exam Questions
NEW QUESTION # 28
Which of the following metrics are mandatory in a service manifest? Note: There are 3 correct Answers to this question.
- A. ap Version
- B. Type
- C. Kind
- D. Ports
- E. Cluster IP
Answer: C,D,E
NEW QUESTION # 29
What does a pod in Kubernetes represent?
- A. Smallest deployable units in Kubernetes
- B. Container for exactly one application
- C. Thin wrapper around multiple deployments
- D. Virtual operating system
Answer: A
NEW QUESTION # 30
Which kubectl command updates objects?
- A. kustomize <filename> yaml
- B. create - <filename> yam
- C. apply -f <filename>.yaml
Answer: C
Explanation:
Explanation
Use kubectl apply to create or update resources from a file or stdin. This command does a three-way diff between the previous configuration, the input configuration, and the current configuration of the resource, and then applies the changes.
Use kubectl patch to update Kubernetes API objects in place. Do a strategic merge patch or a JSON merge patch.
Use kubectl replace to delete and re-create the resource. You can use this command to update immutable fields of a resource, such as its kind or name.
References:
Manage Kubernetes Objects
Command line tool (kubectl)
kubectl Quick Reference
NEW QUESTION # 31
What are some primitives that can be used to manage storage in a Kubernetes cluster? Note: There are 3 correct Answers to this question.
- A. Volumes
- B. Persistent Volumes
- C. Volume Snapshot Classes
- D. Storage Classes
- E. Config Maps
Answer: A,B,D
Explanation:
Explanation
Kubernetes provides several primitives to manage storage in a cluster, such as Volumes, Persistent Volumes, Storage Classes, and Volume Snapshot Classes. Volumes are the basic unit of storage that can be attached to a Pod and provide data persistence across Pod restarts. Persistent Volumes are cluster-wide resources that represent a piece of storage that has been provisioned by an administrator or dynamically using Storage Classes. Storage Classes are a way for administrators to describe the classes of storage they offer and allow users to request a specific class for their Persistent Volume Claims. Volume Snapshot Classes are a way to specify different policies for creating volume snapshots, such as retention, encryption, or replication. References: https://kubernetes.io/docs/concepts/storage/storage-classes/
https://kubernetes.io/docs/concepts/storage/persistent-volumes/
NEW QUESTION # 32
Which of the following technologies does the Kyme Eventing process use? Note: There are 3 correct Answers to this question.
- A. HTTP-post requests
- B. Apache Kafka
- C. NATS
- D. MQTT
- E. Jet Stream
Answer: A,C,E
NEW QUESTION # 33
What are some primitives that can be used to manage storage in a Kubernetes cluster? Note: There are 3 correct Answers to this question.
- A. Volumes
- B. Persistent Volumes
- C. Volume Snapshot Classes
- D. Storage Classes
- E. Config Maps
Answer: A,B,D
NEW QUESTION # 34
When do you use a Daemon Set as the main workload type?
- A. To run multiple instances of the same container
- B. To run a workload on every node in the cluster
- C. To run a batch job
Answer: B
NEW QUESTION # 35
When would you use kubect!? Note: There are 3 correct Answers to this question.
- A. To deploy containers into production clusters
- B. To forward ports from remote machines to pods
- C. To plot time series data
- D. To view pod logs
- E. To run interactive commands
Answer: B,D,E
Explanation:
Explanation
kubectl is a command-line tool that allows you to run commands against Kubernetes clusters1. You can use kubectl in SAP BTP, Kyma runtime for the following purposes:
To run interactive commands. kubectl supports various commands that let you interact with your cluster resources, such as creating, updating, deleting, describing, or executing them. For example, you can use kubectl create to create a resource from a file or kubectl exec to run a command in a container2.
To view pod logs. kubectl allows you to view the logs of a pod or a container in a pod using the kubectl logs command. This can help you troubleshoot issues or monitor the pod activity3.
To forward ports from remote machines to pods. kubectl enables you to forward one or more local ports to a pod using the kubectl port-forward command. This can allow you to access a pod from your local machine for debugging or testing purposes4.
References:
1: Kubernetes / Overview of kubectl
2: Kubernetes / kubectl Cheat Sheet
3: Kubernetes / Viewing logs
4: Kubernetes / Use Port Forwarding to Access Applications in a Cluster
NEW QUESTION # 36
What are some of the components of the architecture of a Kubernetes cluster? Note: There are 3 correct Answers to this question.
- A. kube-apl
- B. kube-proxy
- C. etcdprovider
- D. etod
- E. kubelet
Answer: B,D,E
NEW QUESTION # 37
When you create an API Rule for a service, what is created automatically?
- A. An Istio Virtual Service
- B. A Kubernetes Service
- C. A Helm Chart
- D. A Kubernetes Deployment
Answer: A
Explanation:
Explanation
When you create an API Rule for a service, the API Gateway Controller creates an Istio Virtual Service for you behind the kyma-gateway. The Istio Virtual Service defines the rules that control how requests for a service are routed within an Istio service mesh. By creating an API Rule, you have a higher-level abstraction of Istio VirtualServices and Oathkeeper Access Rules that allows you to provision services quickly and securely. References: Using the API Gateway to Expose Services, Exposing a Service in Kyma with API Rules
NEW QUESTION # 38
What are some parts of a pod object? Note: There are 3 correct Answers to this question.
- A. metadata
- B. kubelet
- C. ap Version
- D. kind
- E. etod
Answer: A,C,D
Explanation:
Explanation
A pod object is a Kubernetes resource that represents a group of one or more containers that share storage and network resources, and a specification for how to run the containers. A pod object has the following parts:
kind: This is the type of the resource, which is always Pod for pod objects.
ap Version: This is the version of the API that the pod object uses, which is usually v1 for pod objects.
metadata: This is a set of data that identifies and labels the pod object, such as name, namespace, labels, and annotations.
The other options are not parts of a pod object, but they are related to other Kubernetes concepts:
etod: This is a misspelling of etcd, which is a key-value store that holds the cluster data, such as pod objects, but it is not part of the pod object itself.
kubelet: This is an agent that runs on each node in the cluster and communicates with the control plane.
The kubelet is responsible for creating, starting, and deleting pod objects on the node, but it is not part of the pod object itself.
References: Side-by-Side Extensibility Based on SAP BTP, Kyma Runtime - Unit 2 - Lesson 1: Kubernetes and Kyma Core Concepts, Kubernetes Documentation - Pods, Kubernetes Documentation - Kubernetes Objects.
NEW QUESTION # 39
What can be increased or decreased with Horizontal Pod Auto scalers?
- A. The resources of pods
- B. The number of pods
- C. The lifetime of pods
Answer: B
NEW QUESTION # 40
What are some benefits of using the Istio service mesh in SAP BTP, Kyma runtime? Note: There are 3 correct Answers to this question.
- A. Mutual TLS is supported for service to service communication.
- B. Networking is coupled to the application logic.
- C. Traffic management between services can be controlled.
- D. Distributed tracing can be used to trace request flows.
- E. Networking is decoupled from the application logic.
Answer: A,C,E
Explanation:
Explanation
Istio is a service mesh that provides a uniform way to secure, connect, and monitor microservices running on different platforms and environments1. SAP BTP, Kyma runtime uses Istio as the default service mesh solution to enable the following benefits2:
Networking is decoupled from the application logic. Istio handles the network traffic between services using a data plane composed of Envoy proxies that are injected as sidecars to each service Pod. This way, the application code does not need to deal with networking aspects such as routing, load balancing, authentication, or encryption3.
Mutual TLS is supported for service to service communication. Istio enables mutual TLS (mTLS) by default for all services in the mesh, ensuring that the traffic is encrypted and authenticated. Istio also manages the certificates and keys for mTLS using a control plane component called Istiod4.
Traffic management between services can be controlled. Istio allows defining and applying traffic policies, such as timeouts, retries, circuit breakers, fault injection, mirroring, or routing rules, using custom resources such as VirtualServices and DestinationRules. These policies can be dynamically configured and updated without requiring service restarts.
References:
1: Discovering Istio - SAP Learning
2: Upcoming breaking change in SAP BTP, Kyma Runtime: Enabling the Istio CNI plugin | SAP Blogs
3: Istio / The Istio service mesh
4: Istio / Secure your service mesh
[5]: Istio / Traffic management overview
NEW QUESTION # 41
Which workload type is used to create time-based jobs?
- A. StatefulSet
- B. CronJob
- C. Deployment
- D. Job
Answer: B
NEW QUESTION # 42
What are some features of Kubernetes? Note: There are 3 correct Answers to this question.
- A. Extensibility and ecosystem
- B. Process management and optimization
- C. Integration and assessment
- D. Immutability and self-healing
- E. Automated rollouts and rollbacks
Answer: A,D,E
Explanation:
Explanation
Some of the features of Kubernetes are:
Immutability and self-healing: Kubernetes treats pods as immutable, meaning that they are not modified after they are created. Instead, pods are replaced with new ones when they need to be updated or repaired. This ensures that the pods are always in a consistent and predictable state. Kubernetes also monitors the health and availability of the pods and automatically restarts, reschedules, or replicates them if they fail or become unresponsive1.
Extensibility and ecosystem: Kubernetes is designed to be extensible and modular, allowing users to customize and extend its functionality according to their needs. Kubernetes supports various extensions, such as custom resources, operators, admission controllers, schedulers, network plugins, storage plugins, and more. Kubernetes also has a large and vibrant ecosystem of tools, services, and applications that are built on top of or integrate with it2.
Automated rollouts and rollbacks: Kubernetes enables users to deploy and update their applications with zero downtime, using declarative configuration and rolling updates. Kubernetes ensures that only a certain number of pods are changed at a time, and that the new pods are ready before terminating the old ones. Kubernetes also tracks the history of each update and allows users to roll back to a previous version if something goes wrong3.
References:
1: Pods | Kubernetes
2: Extending Kubernetes | Kubernetes
3: Deployments | Kubernetes
NEW QUESTION # 43
Which of the following does Kyma Eventing simplify? Note: There are 2 correct Answers to this question.
- A. Sending Cloud Events to the NATS backend without proxy
- B. Connecting event publishers and subscribers directly
- C. Publishing events
- D. Subscribing to events
Answer: C,D
Explanation:
Explanation
Kyma Eventing simplifies the process of publishing and subscribing to events in the cluster. Publishing events means sending information about a change in the state of the application or the system to the Eventing backend. Subscribing to events means registering interest for a specific event type from a specific source.
Kyma Eventing allows users to publish events by sending HTTP requests to the Event Publisher Proxy component, which validates and forwards the events to the NATS backend. Kyma Eventing also allows users to subscribe to events by creating Subscription custom resources that specify the event source, type, and the HTTP endpoint of the service that will receive the events. Kyma Eventing handles the delivery of the events from the NATS backend to the subscribers with the help of the Eventing Controller and the Eventing Dispatcher components. References: https://kyma-project.io/
https://blogs.sap.com/2021/06/15/in-cluster-eventing-in-sap-btp-kyma-runtime/
NEW QUESTION # 44
What is the secret and configuration management feature in Kyma?
- A. A configuration assistant
- B. An object store
- C. A local password manager
- D. A credential store and manager
Answer: D
Explanation:
Explanation
Kyma uses Kubernetes secrets as the secret and configuration management feature. A secret is an object that contains sensitive data, such as passwords, tokens, or keys, that can be accessed by authorized pods or users.
Secrets can be created manually, generated dynamically, or imported from external sources. Kyma provides a custom resource (CR) called ServiceBinding that allows you to create secrets for service instances and inject them into your workloads. You can also use the Service Catalog UI or the Service Management CLI to manage your secrets123. References: Secrets | Kubernetes, Service Binding | SAP Help Portal, Service Catalog
| SAP Help Portal, Service Management CLI | SAP Help Portal
NEW QUESTION # 45
Which tool does SAP BTP, Kyma runtime use for log collection?
- A. Kiali
- B. Fluent Bit
- C. Jaeger
- D. Prometheus
Answer: B
NEW QUESTION # 46
Which of the following are parts of the architecture of the SAP BTP Service Operator for Kubernetes? Note:
There are 2 correct Answers to this question.
- A. kubelet
- B. API server
- C. Storage system
- D. Service broker
Answer: B,D
Explanation:
Explanation
The SAP BTP Service Operator for Kubernetes is a Kubernetes operator that enables you to consume SAP BTP services from your Kubernetes cluster using Kubernetes-native tools. It communicates with the Service Manager, which acts as an intermediary for the Kubernetes API server to negotiate the initial provisioning and retrieve the credentials necessary for the application to use a managed service. The Service Manager uses the Open Service Broker API to communicate with service brokers, which are responsible for managing the lifecycle of service instances and bindings12. The following diagram illustrates the architecture of the SAP BTP Service Operator for Kubernetes1:
As you can see, the architecture of the SAP BTP Service Operator for Kubernetes consists of the following parts12:
API server: The API server is the main component of the Kubernetes control plane. It exposes the Kubernetes API and handles the requests from the clients, such as kubectl or the SAP BTP Service Operator. The API server also interacts with the etcd, which is the persistent storage for the cluster data.
SAP BTP Service Operator: The SAP BTP Service Operator is a custom controller that watches the Kubernetes API server for changes to the custom resources (CRs) that represent the SAP BTP service instances and bindings. It reconciles the desired state of the CRs with the actual state of the SAP BTP services by calling the Service Manager API.
Service Manager: The Service Manager is a component of SAP BTP that acts as a proxy between the SAP BTP Service Operator and the service brokers. It provides a unified API for managing service instances and bindings across different platforms and environments. It also handles the authentication and authorization of the requests from the SAP BTP Service Operator.
Service Broker: The service broker is a component that implements the Open Service Broker API and provides the logic for provisioning, deprovisioning, binding, and unbinding service instances. The service broker can be either a native SAP BTP service broker or a third-party service broker that is registered in the Service Manager. References: Introducing SAP BTP Service Operator | SAP Blogs, Working with SAP BTP Service Operator | SAP Help Portal, SAP/sap-btp-service-operator - GitHub
NEW QUESTION # 47
What does a service mesh in Kyma typically consist of? Note: There are 2 correct Answers to this question.
- A. Data plane
- B. Control plane
- C. Worker node
- D. Master node
Answer: A,B
NEW QUESTION # 48
In which order are pods created when a StatefulSet is set up?
- A. Consecutive
- B. Chronological
- C. Sequential
Answer: C
Explanation:
Explanation
Pods are created in a sequential order when a StatefulSet is set up. This means that for a StatefulSet with N replicas, the Pods are deployed one by one, starting from the Pod with the index 0 and ending with the Pod with the index N-1. Each Pod has to be in the Running and Ready state before the next Pod is created. This ensures that the Pods have a predictable and unique identity and can be connected to their corresponding persistent volumes. References: https://www.howtoforge.com/create-a-statefulset-in-kubernetes/
https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/
NEW QUESTION # 49
You have deployed a workload through a Kubernetes Deployment to SAP BTP, Kyma runtime. What must you do to expose the workload to the public internet? Note: There are 3 correct Answers to this question.
- A. Create an API Rule CR.
- B. Add a custom Virtual Service CR to secure the service.
- C. Add a readiness probe for your workload.
- D. Create a service to group your pods.
- E. Configure rules and access Strategies.
Answer: A,C,E
NEW QUESTION # 50
......
C_KYMD_01 Dumps 100 Pass Guarantee With Latest Demo: https://topexamcollection.pdfvce.com/SAP/C_KYMD_01-exam-pdf-dumps.html