C1000-010 · Question #30
Ruleset parameters can be defined for a ruleset or decision service, and the parameters can have different directions such as IN, OUT, or IN_OUT. If the decision service being invoked includes all…
The correct answer is C. Both output and input-output parameters need to be provided in the request. Option C is correct because when invoking a decision service, OUT and IN_OUT parameters must both be physically present in the request payload. OUT parameters must appear as placeholder containers so the decision service has an object to write results into and return; IN_OUT…
Question
Ruleset parameters can be defined for a ruleset or decision service, and the parameters can have different directions such as IN, OUT, or IN_OUT. If the decision service being invoked includes all three different types of parameters, which statement is true?
Options
- AOnly the input parameter needs to be provided in the request.
- BOnly the input-output parameter need to be provided in the request.
- CBoth output and input-output parameters need to be provided in the request.
- DBoth input and input-output parameters have to be provided in the request.
How the community answered
(35 responses)- A3% (1)
- B17% (6)
- C71% (25)
- D9% (3)
Explanation
Option C is correct because when invoking a decision service, OUT and IN_OUT parameters must both be physically present in the request payload. OUT parameters must appear as placeholder containers so the decision service has an object to write results into and return; IN_OUT parameters must be included with their initial values since the service reads them on the way in and writes back modified values on the way out. Purely IN parameters, by contrast, are handled through a different part of the invocation - their values flow into the ruleset but do not require a request-level container object in the same way.
- A is wrong because providing only IN parameters leaves no containers for outputs; the service can't return OUT or IN_OUT results if they aren't represented in the request.
- B is wrong because IN_OUT alone is insufficient - OUT parameter containers must also be in the request for the service to populate and return them.
- D is wrong because IN parameters don't need to be explicitly included in the request object alongside IN_OUT parameters; it conflates which directions require request-level presence.
Memory tip: Think of it as "what does the caller need to set up before the service runs?" - OUT needs an empty bucket (container), IN_OUT needs a pre-filled bucket (initial value + return slot). IN values are already "known" to the caller and handled differently. So OUT + IN_OUT = what goes in the request.
Topics
Community Discussion
No community discussion yet for this question.