Which tool does SAP BTP, Kyma runtime use for log collection?
Options:
A.
Jaeger
B.
Prometheus
C.
Kiali
D.
Fluent Bit
Answer:
D
Explanation:
Explanation:
SAP BTP, Kyma runtime uses Fluent Bit as the tool for log collection. Fluent Bit is an open-source log processor and forwarder that allows you to collect data and logs from different sources, enrich them with filters, and send them to multiple destinations. Fluent Bit is deployed as a DaemonSet on every node of the Kyma runtime cluster, and collects logs from the containers running on the node. Fluent Bit forwards the logs to Loki, a log aggregation system that is compatible with Prometheus12. References: Fluent Bit, Logging | SAP Help Portal.
Question 17
Which command lists the pods in a specific namespace?
Options:
A.
kubectl get pods -n
B.
kubectl print pods n
C.
kubectl list pods n
D.
kubectl show pods -n
Answer:
A
Explanation:
Explanation:
The command kubectl get pods -n lists the pods in a specific namespace. This command uses the -n flag to specify the namespace and the get pods subcommand to retrieve the pod resources. The output shows the name, status, restarts, and age of each pod in the namespace1. You can also use the -o wide flag to show more details, such as the node where the pod is running2. References:
1: Get a Shell to a Running Container
2: List pods per namespace in kubernetes
Question 18
For which workload requirements would you use StatefulSet? Note: There are 3 correct Answers to this question.
Options:
A.
Ordered, graceful deployment and scaling
B.
Stable, persistent storage
C.
Ordered network identifiers
D.
Stable, unique network identifiers
E.
Ordered, persistent storage
Answer:
A, B, D
Explanation:
Explanation:
A StatefulSet is a workload type that runs one or more pods that maintain a stable identity and persistent storage1. StatefulSets are suitable for applications that require one or more of the following2:
Ordered, graceful deployment and scaling: StatefulSets ensure that pods are created and deleted in a sequential, ordered manner. Pods are assigned ordinal numbers that reflect their order in the set. Pods are scaled in reverse order of creation. StatefulSets also respect pod disruption budgets to limit the number of pods that are down simultaneously.
Stable, persistent storage: StatefulSets use PersistentVolumeClaims to provide each pod with its own persistent storage. The PersistentVolumeClaim of a pod is not deleted when the pod is deleted, which preserves the state of the application across pod rescheduling.
Stable, unique network identifiers: StatefulSets use a headless service to provide each pod with a unique network identity. Pods have a stable hostname based on their ordinal number and the name of the StatefulSet. Pods can use this hostname to communicate with each other and access their own or other pods’ data.