A city agency wants a score for permits likely to be abandoned. The strongest lab model needs the applicant's private credit score, which the agency is not allowed to collect. A model using only fields already on the permit form still beats the clerks' current review. What should the team recommend?
Select an answer to reveal the explanation.
Short Explanation
A recipe that calls for an ingredient you are forbidden to buy is not one you can serve. You recommend the permit-form model and drop the design that needs a credit score the agency cannot collect. The trap is keeping the lab winner because its score used a field you will not have in production.
Full Explanation
A design that requires a feature the business cannot collect cannot be the system you tell them to run. The credit score is legally unavailable, so the lab model that needs it is not a recommendation, however strong it looked where that column existed. The permit-form model uses fields the agency already has and beats the current clerk review, so it is the design that can change the decision now. A higher lab number that depends on a forbidden column is a research note, not a system the permit desk can run. Holding go-live for a credit score the agency may not collect still recommends the unavailable design and delays a usable one. Leaving the credit field blank in production feeds the lab model an input it was not built to miss, and it still commits to a feature the forms do not have. Recommending no model ignores a form-only model that already beats today's review. Exam caveat: a feature that becomes collectable later can enter a future design; it cannot be required in the design you recommend now. Operational check: confirm the recommended feature list contains only columns present on the permit form.