SAP C_KYMD_01 Exam With Confidence Using Practice Dumps

 The service mesh solution in SAP BTP, Kyma runtime is based on Istio, which is one of the most popular service mesh solutions. Istio uses the Sidecar proxy pattern, which means that a proxy is deployed as a sidecar container next to each service. This way, the proxy can intercept and manage the traffic between the services, without requiring any changes in the application code. The proxy also communicates with the Istio control plane, whichprovides configuration and policies for the service mesh. The other options are not valid proxy patterns for the service mesh solution in SAP BTP, Kyma runtime. References: Discovering the Service Mesh - SAP Learning, Istio Documentation - What is Istio?

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: 

• A headless service is defined by setting the clusterIP field to None in the service spec. This tells Kubernetes not to allocate a cluster IP for the service, and to create DNS records only.
• For StatefulSets, you can use a headless service to control the domain of the pods. The pods that belong to a StatefulSet have a unique identity that is comprised of an ordinal, a stable network identity, and stable storage. The identity sticks to the pod, regardless of which node it’s (re)scheduled on.
• Each pod in a StatefulSet derives its hostname from the name of the StatefulSet and the ordinal of the pod. The pattern for the constructed hostname is (statefulsetname)−(ordinal). The example above will create three pods named web-0,web-1,web-2.
• A StatefulSet can use a headless service to provide network identity for its pods. The service is responsible for creating a DNS record for each pod in the form (podname).(governing service domain). For the previous example, the headless service named nginx will create DNS records for web-0.nginx, web-1.nginx, and web-2.nginx.

References:

• Headless Services
• StatefulSets
• Is it required to use a headless service for statefulsets?