I disagree. You asked for two required key/value pairs, one with name literally 'input1' and the other with name literally 'input2', and you asked the the corresponding value for each be of type character. You then ask to parse upon input 'AUDI', 1 . The strings 'input1' and 'input2' are not present, so an error needs to be generated .
If the user had passed in 'input2', 'hello' then that would have matched the required parameter 'input2' but would have failed because it was missing the required 'input1'
You will never be able to match two mandatory property/value pairs without allowing at least four inputs instead of two.
The KeepUnmatched does not override the need for mandatory parameters: instead it allows you to get clean control of additional parameters after all mandatory and optional parameters have been handled.
Your code is confusing to users because you use the variable names input1 and input2 as well as happening to look for the literal strings 'input1' and 'input2', but those are different domains. It's like naming your cat "dog" and then calling out "Here dog!" and expecting your cat to know the difference between that and "Here 'dog'!" (in the first of those you are calling for the dog, but in the second of those you are calling for the thing named 'dog', which is a cat.)