What are some primitives that can be used to manage storage in a Kubernetes cluster? Note: There are 3 correct Answers to this question.
Correct Answer: A,C,E
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/
Question 2
What are some features of Kubernetes? Note: There are 3 correct Answers to this question.
Correct Answer: A,B,D
Question 3
What are some benefits of using the Istio service mesh in SAP BTP, Kyma runtime? Note: There are 3 correct Answers to this question.
Correct Answer: A,C,E
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
Question 4
Using the Cloud Events specification, which component must you use to post events to Kyma Eventing?
Correct Answer: A
Explanation To post events to Kyma Eventing using the Cloud Events specification, you need to use the service/eventing-event-publisher-proxy component. This component is responsible for validating and forwarding events to the Eventing Controller, which then dispatches them to the subscribers. The other components are not relevant for this purpose. The pod/eventing-event-publisher-proxy is the name of the pod that runs the service, but it is not the component that you use to post events. The pods/eventing-nats-0 and svc/eventing-nats are related to the NATS eventing framework, which is the default eventing backend in Kyma, but they are not the components that you use to post events using the Cloud Events specification. References: Side-by-Side Extensibility Based on SAP BTP, Kyma Runtime - Unit 4 - Lesson 1: Eventing in Kyma, Kyma Documentation - Event Publisher Proxy
Question 5
Which open-source project is one part of the API Gateway in Kyma?
Correct Answer: D
Explanation The API Gateway in Kyma is a custom-configured Istio Ingress Gateway that is installed in the kyma-system namespace called kyma-gateway. Istio is an open-source project that provides a service mesh for microservices. It enables traffic management, security, observability, and policy enforcement for the services in the cluster. The API Gateway uses Istio resources to expose and secure APIs for the workloads in Kyma. References: Using the API Gateway to Expose Services, SAP BTP, Kyma Runtime API Gateway future architecture based on Istio, GitHub - kyma-project/api-gateway.
