Question 390
An Azure ML pipeline uses a component input declared optional. A missing binding makes the script fall back to production data, even for development tests. How should the interface behave?
Explanation
Correct Answer
Optional inputs should not silently bypass environment isolation; a governed data contract must make source selection intentional.
Incorrect Answers
Hiding validation messages does not prevent the undesired production data access.
Expanded access can disguise an unsafe default rather than enforce the correct input.
Optionality does not authorize substituting protected production records for development inputs.