Hey @JuanEdRomGlobal
Thanks for identifying that bare/stable inconsistency – fixed!
As for the job failure, this is a bit of a red herring. It likely “failed” due to a warning regarding a deprecated option in our automation plan. However, the ZAP scan will still have run successfully and produced the report artifact required to complete the lab. Of course, that’s not great, since we don’t disclaim that, and our screenshot shows all jobs as green (unequivocal success). I’ve fixed this error by specifying the exact ZAP docker image we want to use, instead of letting Docker just pull the latest.
Anywho, I’ve published these changes so you should be all set now 
Happy hacking!