Q: 6
When you create an API Rule for a service, what is created automatically?
Options
Discussion
B not D. A lot of folks pick D because "Service" sounds right for Kubernetes, but API Rule means Istio VirtualService gets spun up automatically. Seen this on similar practice exams; open to being corrected if there's a Kyma quirk.
B tbh. When you set up an API Rule in Kyma, it actually creates an Istio VirtualService to manage the traffic routing and policies. K8s Service (D) would be for basic Kubernetes exposure, but here the API Rule specifically triggers the creation of Istio resources. Pretty sure that's what SAP's doing under the hood here.
D imo. If you're exposing something, you'd expect a K8s Service gets created for routing, right? Unless they're specifically using Istio, but the basic resource would be Service in most vanilla Kubernetes setups. Maybe I'm missing some SAP magic though.
Likely D here. When I think about creating something to expose a service in standard Kubernetes, that's normally a Service, not Istio stuff. Unless they're calling out the Kyma specifics, I'd still pick D over B. Could be missing some SAP-specific detail though.
B not D
I see why people say D here. Creating an API Rule makes me think a Kubernetes Service would pop up automatically.
Maybe D in this case. API Rule sounds like something that needs a Service to expose pods in vanilla K8s, and most practice tests try to trick you with that. Not sure if Istio gets built every time unless Kyma is clearly mentioned. Open to correction if I'm missing how SAP wires this.
D or B. I figure creating an API Rule should spin up a Kubernetes Service automatically since that's how most things get exposed in K8s. Maybe SAP's Kyma layer uses Istio under the hood, but I don't see why you'd skip the Service. Someone correct me if I'm off here.
Probably B. In these SAP CAP/Kyma setups, creating an API Rule usually instantiates an Istio VirtualService for the routing and traffic policies. Option D is tempting since Services are classic Kubernetes, but here the API Rule is more tied to Istio resources. Unless I'm off on a detail.
Why is SAP always hiding these K8s details behind layers of abstraction? B
Be respectful. No spam.
