Q: 12
Which expression language can you use to access the content of a message in an integration flow?
Options
Discussion
Option D Spring EL (C) pops up in SAP docs too but it doesn't directly handle message content inside integration flow config, that's why D fits. Seen a similar trap before.
Option D, Simple expression language is the one used for this in SAP CPI, not the others.
D , Simple expression language is what SAP CPI uses throughout most integration flow steps to access message content. You’ll see the ${...} syntax all over config fields for headers/properties/body, it’s built on Apache Camel’s Simple EL. Spring EL (C) gets mentioned but isn’t standard for this use. Pretty sure D is best unless they specifically mention a scripting context.
I always thought B, since XML is what you're processing most of the time in iFlows.
D
Yeah, SAP CPI uses Simple expression language for accessing message content, so D is correct here.
Pretty certain it’s D, Simple expression language. That’s what’s built into SAP CPI for grabbing message content like ${body} or headers. Not seen the other languages used natively in iFlow configs. Anyone disagree?
D
D , encountered exactly similar question in my exam-Simple expression language is the expected pick for standard integration flow fields in SAP CPI.
D imo , but only if they're talking about standard config fields. If they sneak in something about script steps where JavaScript or Spring EL can be used, the answer flips. Saw a similar edge case on a practice test.
Be respectful. No spam.
