Pier-light-outage scoring runs all night. A one-off notebook comparison was run after a complaint and then forgotten. Official Model Monitor skill includes a repeating schedule. What should they create?
Select an answer to reveal the explanation.
Short Explanation
A one-off notebook comparison was run after a complaint and then forgotten. Create a Model Monitor schedule, hourly or daily, that analyzes captures and writes reports. Another one-off after the next complaint is the failure, and a CodePipeline merge is not that schedule.
Full Explanation
Create a Model Monitor schedule so analysis repeats (hourly or daily) and writes reports. An ad-hoc notebook after a complaint is forgotten. Polly is not a cadence, and a CodePipeline merge is not that monitor schedule.