Q: 9
What are some advantages of creating an OData interface through an API pro-vider? Note: There are
2 correct answers to this question.
Options
Discussion
D . OpenAPI spec and Swagger UI are what SAP generates for OData APIs, not WSDL or RAML.
C/D. Pretty sure it's not B, since RAML isn't auto-generated with SAP's API provider for OData. WSDL (A) is more for SOAP, so I don't think that's a trap here. Seen similar questions on practice exams too.
B tbh, since RAML is used for API design and some platforms generate it automatically. I know SAP usually uses OpenAPI/Swagger but the question just asks about any API provider, so B seemed plausible at first glance. Could be a trick though.
D imo, SAP auto-generates Swagger UI and OpenAPI spec for OData interfaces.
Probably C and D, that's what the official guide and practice tests always say for SAP OData APIs. OpenAPI spec and Swagger UI get generated, but not WSDL or RAML. If anyone's seen different in real labs, let me know.
Its D and C, not B. RAML can be a trap here, SAP's API provider for OData makes OpenAPI spec and Swagger UI by default. Saw this tested in several practice sets.
C/D imo, that's what the official guide and most SAP practice tests say for API provider and OData. Swagger UI and OpenAPI are generated automatically, but never saw RAML or WSDL come up for this combo. Correct me if I'm off.
Looks like it's C and D here. SAP API providers automatically generate an OpenAPI spec and a Swagger UI for OData services, so those options fit the usual behavior. WSDL and RAML are for other protocols or aren't the native output in this setup. If someone has seen a different default in SAP, let me know, but I think C/D are right.
For me, C and D here. WSDL is more for SOAP, and RAML isn't default for OData APIs with SAP providers. Swagger UI and OpenAPI spec are pretty much auto-generated, at least with Integration Suite. If someone has seen B working in this context let me know, but I'm sticking with C/D for now.
C , but only if the API provider supports interactive documentation. D is valid because OpenAPI spec gets built out automatically for OData. Edge case: sometimes Swagger UI won't be there if disabled. Anyone disagree?
Be respectful. No spam.
