A retailer turns a finance AI feature on in the production company before any test company has run it. Controllers see the new guidance during the live close. What should the architect require?
Select an answer to reveal the explanation.
Short Explanation
You do not flip the store's price file during Saturday trade and call that the rehearsal. You require a passing run in the test company before the production feature flag moves. A complaint after go-live is the incident, not the test.
Full Explanation
Finance AI changes belong in a test company before they touch the production company. This feature was turned on in production with no test company run, and the live close became the first test. The architect requires a passing run in the test company before the production feature flag is moved, so controllers see the guidance in test data first. Turning the feature on in production and opening a test company only after a complaint repeats the same order and uses live close as the detector. Piloting inside a seller's personal spreadsheet skips the finance company, the copilot, and the close process the feature actually changes. Leaving the feature on in production and deleting the test company removes the only safe place to run the next change. Exam caveat: a test company pass is about this feature in test data. It does not prove every other finance feature is ready, and it does not replace the promotion path. Operational check: run the feature in the test company, record the pass, and confirm the production flag stays off until that pass is on the release record.