[2024年03月23日] C_KYMD_01 PDFで最近更新された問題です集試験点数を伸ばそう
C_KYMD_01完全版問題集には無料PDF問題で合格させる
質問 # 10
What are some characteristics of the API Gateway? Note: There are 2 correct Answers to this question.
- A. It is the central point of contact for all internal traffic in the Kyma cluster.
- B. It uses Envoy Proxy to handle traffic and forward it to the correct service
- C. It uses Ory Oath keeper to manage access to services.
- D. It uses a custom-configured Nginx Ingress Gateway.
正解：A、B
解説：
Explanation
The API Gateway is a component that enables exposing and securing services outside the Kyma cluster using the APIRule custom resource (CR)1. The API Gateway has the following characteristics:
It is the central point of contact for all external traffic that enters the Kyma cluster. The API Gateway is a custom-configured Istio Ingress Gateway that is installed in the kyma-system namespace called kyma-gateway2. The kyma-gateway acts as a reverse proxy that routes the incoming requests to the appropriate services based on the host name and the path specified in the APIRule CR3.
It uses Envoy Proxy to handle traffic and forward it to the correct service. The API Gateway is based on the Istio Gateway, which is a load balancer that operates at the edge of the mesh and enables ingress and egress traffic for the cluster. The Istio Gateway is implemented by a pod that runs an Envoy Proxy container, which is responsible for receiving and forwarding the traffic according to the Istio routing rules.
References:
1: Kyma / API Gateway v2
2: Using the API Gateway to Expose Services - SAP Learning
3: SAP BTP, Kyma Runtime API Gateway future architecture based on Istio | SAP Blogs
[4]: Istio / Gateway
[5]: Istio / Envoy
質問 # 11
When you create an API Rule for a service, what is created automatically?
- A. An Istio Virtual Service
- B. A Helm Chart
- C. A Kubernetes Service
- D. A Kubernetes Deployment
正解：A
解説：
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
質問 # 12
What are some features of Kubernetes? Note: There are 3 correct Answers to this question.
- A. Integration and assessment
- B. Immutability and self-healing
- C. Process management and optimization
- D. Automated rollouts and rollbacks
- E. Extensibility and ecosystem
正解：B、D、E
質問 # 13
Which command lists the pods in a specific namespace?
- A. kubectl show pods -n <namespace>
- B. kubectl get pods -n <namespace>
- C. kubectl list pods n <namespace>
- D. kubectl print pods n <namespace>
正解：B
質問 # 14
Where can you check which SAP BTP services are available to create in your subaccount?
- A. SAP Help Desk
- B. SAP Discovery Center
- C. SAP Community
- D. SAP BTP Service Marketplace
正解：D
質問 # 15
Which Prometheus component must you create to scrape metrics from targets you want to observe?
- A. Service Monitor CRD
- B. Pod Monitor CRD
- C. Service Manifest
正解：A
解説：
Explanation
To scrape metrics from targets you want to observe, you need to create a Service Monitor Custom Resource Definition (CRD) in Prometheus. A Service Monitor CRD defines the endpoints, ports, paths, and labels of the targets that expose metrics in a standard Prometheus format. The Service Monitor CRD also specifies how often the targets should be scraped and what relabeling rules should be applied. The Service Monitor CRD is automatically detected and processed by the Prometheus Operator, which creates the appropriate scrape configurations for Prometheus. The other options are not valid components for scraping metrics from targets.
A Pod Monitor CRD is similar to a Service Monitor CRD, but it defines the pods that expose metrics, rather than the services. A Service Manifest is a YAML file that defines the service type, version, and metadata, but it does not specify the metrics endpoints or scraping parameters. References: Side-by-Side Extensibility Based on SAP BTP, Kyma Runtime - Unit 4 - Lesson 2: Observability in Kyma, Prometheus Operator Documentation - Service Monitor
質問 # 16
What is a characteristic of Kubernetes pods managed by deployments?
- A. They are assigned a random hash suffix as part of their name.
- B. They have a stable name.
- C. They are stateful.
正解：A
質問 # 17
When you create an API Rule for a service, what is created automatically?
- A. An Istio Virtual Service
- B. A Helm Chart
- C. A Kubernetes Service
- D. A Kubernetes Deployment
正解：A
質問 # 18
Which service does the SAP BTP service operator on SAP BTP, Kyma runtime use to consume services on SAP BTP?
- A. SAP Service Manager
- B. SAP Service Marketplace
- C. SAP API Business Hub
正解：A
質問 # 19
Why is a headless service type recommended for StatefulSets in Kubernetes?
- A. Pods managed by a StatefulSet have randomly named hashes that CANNOT be used by a regular service for load balancing.
- B. StatefulSets require a load balancer with a single IP address to balance traffic across randomly named pods.
- C. Pods managed by a StatefulSet have stable names and can be accessed directly without a service IP address.
正解：C
質問 # 20
Using the Cloud Events specification, which component must you use to post events to Kyma Eventing?
- A. service/eventing-event-publisher-proxy
- B. svc/eventing-nets
- C. pod/eventing event publisher proxy
- D. pods/eventing nats 0
正解：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
質問 # 21
What does a pod in Kubernetes represent?
- A. Container for exactly one application
- B. Thin wrapper around multiple deployments
- C. Smallest deployable units in Kubernetes
- D. Virtual operating system
正解：C
質問 # 22
Which proxy pattern is used by the service mesh solution in SAP BTP, Kyma runtime?
- A. Shared library
- B. Per-Node
- C. Per-Container
- D. Sidecar
正解：D
質問 # 23
Which command lists services in the current namespace?
- A. kubectl list services
- B. kubectl show services
- C. kubectl print services
- D. kubectl get services
正解：D
質問 # 24
What is the kube-scheduler responsible for in a Kubernetes cluster?
- A. To schedule Cron Jobs
- B. To schedule pods to worker nodes
- C. To scale master nodes vertically
- D. To start pods in the master node
正解：B
解説：
Explanation
The kube-scheduler is a control plane process that assigns pods to nodes based on scheduling principles, such as resource requirements, affinity, anti-affinity, and more. The kube-scheduler watches for newly created pods that have no node assigned and selects an optimal node for each pod to run on. The kube-scheduler does not start pods, scale nodes, or schedule Cron Jobs. These are the responsibilities of other components, such as the kubelet, the cluster autoscaler, and the kube-controller-manager. References: Kubernetes Scheduler, kube-scheduler
質問 # 25
......
100%更新されたのはSAP C_KYMD_01限定版PDF問題集：https://www.goshiken.com/SAP/C_KYMD_01-mondaishu.html
無料SAP Certified Development Associate C_KYMD_01公式認定ガイドPDFダウンロード：https://drive.google.com/open?id=1yc24ozKc4R-DgQdWn4i94tBnNnJQMKmw