At a bank, a new analyst receives a feature function and cannot tell which loan columns it requires or which column it returns. What is missing?
Select an answer to reveal the explanation.
Short Explanation
A function without a contract is a machine with the labels scraped off. You need documentation that says which columns go in and what column comes back. An endpoint, a training log, or a license review answers a different question than the one this analyst is stuck on.
Full Explanation
Documentation of a function states the contract: the inputs it expects and the value it returns. The analyst cannot tell which loan columns are required or which column is added, and that contract is exactly the missing piece. A model endpoint lets an application request a score and does not explain this function's arguments or return value. A hyperparameter log preserves depth, rates, or similar training settings from a run, which is a different record from the function's inputs and output. A license review asks whether a library may be shipped, not which columns the function reads and writes. Until that contract is written down, every caller has to read the code or guess, and a guess about loan columns is how a feature step drifts. An endpoint, a training log, and a license review each cover a different operations question on another day, and none of them names the columns this analyst cannot see. Exam caveat: an example call can illustrate the contract, but the requirement is a statement of what is expected and what comes back, readable before the analyst experiments. Operational check: read the function note and confirm it names the required loan columns and the column that is returned, without opening a training log to guess.