Have A Rollback Plan Before Deploy

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-vibecoder-rollback-plan

1. What is the primary purpose of having a rollback plan before deploying an AI-generated application?

   1. To be able to quickly revert to a working state if the new version causes problems
   2. To impress stakeholders with professional development practices
   3. To reduce the amount of code that needs to be written
   4. To ensure the deployment button works correctly

2. What does it mean to 'write the smallest useful scope the agent can finish'?

   1. Use the simplest programming language available
   2. Write code with as few lines as possible regardless of functionality
   3. Ask the AI to generate the minimum number of files for the project
   4. Break down the task into the smallest complete piece that provides value and can be tested

3. Why should you run the result as a user rather than as a 'fan of the tool' when testing an AI-generated application?

   1. Tool fans are more likely to find bugs
   2. Users cannot test applications effectively
   3. Running as a user helps you find issues that actual users will encounter, whereas being a fan might make you overlook problems
   4. Fans of the tool get better testing results

4. What three things should be inspected before sharing an AI-generated deployment?

   1. The developer's resume, project timeline, and budget
   2. The color scheme, font size, and layout
   3. The diff, data access, and failure path
   4. The AI's training data, model version, and API limits

5. What does 'observable' mean in the context of turning an AI demo into a production-ready application?

   1. The application must be open source
   2. The application must have logging and monitoring to understand what it does in production
   3. The application must be visually appealing
   4. The application must be publicly accessible

6. Which of the following best describes a rollback path?

   1. A document explaining how the code was written
   2. A predefined method to return to a previous working state of the application
   3. A list of all previous deployment timestamps
   4. The route users take when they encounter an error

7. The lesson mentions that 'real skill is turning that demo into something observable, reversible, and safe enough for another person to use.' What makes something 'safe enough' for another person?

   1. It has a nice user interface
   2. It runs on popular cloud infrastructure
   3. It doesn't expose sensitive data and has been tested for common failure cases
   4. It was created by a professional developer

8. When deploying an AI-generated application, what question should guide what data the app should NEVER expose?

   1. What data are competitors likely to want?
   2. What is the most impressive data to show users?
   3. What data does the AI model need to function?
   4. What data would cause harm if exposed, such as personal information or secrets?

9. Why are release notes important in the deployment process?

   1. They make the application look more professional
   2. They reduce the need for testing
   3. They inform users and developers about what changed, which is critical when rolling back
   4. They are required by law

10. What is an 'incident' in the context of deployment and rollback planning?

    1. A feature addition to the application
    2. A creative design choice in the user interface
    3. A successful deployment to production
    4. An unexpected problem or failure that requires response and potentially a rollback

11. The lesson compares 'vibe-coding' communities with 'experienced builders.' What do experienced builders understand that vibe-coding communities may overlook?

    1. That deployment is only the beginning and that reversibility matters
    2. That AI will always generate correct code
    3. That code reviews are unnecessary
    4. That one-click deploys are always safe

12. What does it mean for a deployment to be 'reversible'?

    1. The deployment process can be undone, returning the system to a previous state
    2. The code is open source
    3. The application can be reinstalled by users
    4. The application supports undo operations within its interface

13. What test proves that a change works, according to the questions that should guide deployment?

    1. The code compiles without errors
    2. The AI tool says the code is correct
    3. A test that verifies the new functionality actually solves the intended problem as users would experience it
    4. A test that checks the code follows best practices

14. Why is backing up data before deployment a critical part of the rollback plan?

    1. Backups are required by most hosting providers
    2. Backups make deployments run faster
    3. Backups prevent the AI from making mistakes
    4. Backups allow the system to be restored to a known good state if the deployment causes data corruption or loss

15. The lesson notes that tool names, prices, and features change frequently. What should developers do before relying on specific deployment tools or processes?

    1. Avoid using any deployment tools
    2. Verify the current documentation to ensure the tool still works as expected
    3. Assume AI knows the current state of all tools
    4. Use only the most expensive tools