AI and prompt management platforms

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-creators-tools-AI-and-prompt-management-platforms-r9a1-creators

1. A team has 15 prompts stored as strings in a git repository. Two engineers are the only people who edit them. What is the most likely reason they would NOT benefit from a prompt registry yet?

   1. A registry would slow down their current development workflow
   2. The team is too small to justify the overhead of a new tool
   3. The prompts are not yet complex enough to need rollback features
   4. Git already handles 15 prompts efficiently for a small team

2. Which capability is unique to prompt registries and NOT typically offered by standard git repositories?

   1. Collaborative editing permissions
   2. Version history tracking
   3. Built-in evaluation integration and rollback
   4. Branch and merge functionality

3. A company has 30 prompts and three product managers who need to edit them regularly. What is the strongest argument for migrating to a prompt registry?

   1. The company will need to hire more engineers to manage git
   2. Git cannot handle more than 20 files in a repository
   3. Product managers need safe experimentation without risking production code
   4. Prompt registries are required by data privacy regulations

4. What does a prompt registry's 'rollback' feature actually do?

   1. Restores a prompt to a previously saved version and redeploys it
   2. Changes the access permissions on older prompts
   3. Reverts the AI model to a previous version
   4. Deletes all prompts created after a certain date

5. A team configures their prompt registry to deploy changes directly to production without going through their CI pipeline. What is the greatest risk?

   1. The registry will automatically delete old prompts
   2. The team will lose access to version history
   3. Untested or broken prompts could ship to production
   4. The prompts will run slower in production

6. Which statement best describes the relationship between AI capabilities and prompt management platforms?

   1. AI can guarantee that non-engineer edits are safe
   2. AI cannot replace human engineering review of prompt changes
   3. AI can automatically write tests for every prompt change
   4. AI can eliminate the need for evaluation of prompts

7. What is an 'experiment' in the context of prompt management platforms?

   1. The process of deploying prompts to production
   2. A controlled test of different prompt versions against each other
   3. A way to test new AI models on your data
   4. A method for rolling back failed deployments

8. Why might a team choose to keep prompts in git rather than move to a registry?

   1. Registries are more expensive than git hosting
   2. The team has only a few prompts and technical users who are comfortable with git
   3. Git supports more programming languages
   4. Git provides better version control than any registry

9. What does 'deployment' mean for a prompt registry?

   1. Backing up all prompts to cloud storage
   2. Uploading the registry software to a server
   3. Installing new AI models into the registry
   4. Making a prompt version live for AI systems to use

10. A prompt registry offers 'role-based access control' (RBAC). What is the primary purpose of this feature?

    1. To track who viewed each prompt
    2. To automatically assign prompts to team members
    3. To ensure only authorized people can edit or deploy prompts
    4. To generate usage reports for management

11. What is the relationship between prompt evaluation (evals) and prompt registries?

    1. Evals can only run on prompts stored in git
    2. Registries can integrate with evals to test prompt quality automatically
    3. Evals replace the need for registries
    4. Evals are built into every registry automatically

12. A team migrates from storing prompts as code strings to a prompt registry. What is a recommended migration path?

    1. Convert all prompts to a different programming language
    2. Delete all old prompt files immediately after migration
    3. Import existing prompts into the registry while maintaining parallel testing
    4. Hire a new team to rewrite all prompts from scratch

13. What happens if a non-engineer edits a prompt directly in a registry without any testing?

    1. The prompt could produce harmful or poor outputs when deployed
    2. The AI will refuse to use the prompt
    3. The registry automatically corrects any errors
    4. The edit will be rejected by the system

14. When comparing three different prompt registries, what are the most important criteria to evaluate?

    1. Color scheme, logo design, and company location
    2. Versioning, eval integration, role-based access, and rollback capabilities
    3. Supported programming languages and API rate limits
    4. Number of employees at the company, funding amount, and office size

15. What does it mean that a prompt registry provides 'versioning'?

    1. It tracks every change to prompts with history and the ability to revert
    2. It automatically updates prompts when AI models change
    3. It prevents any changes from being made to prompts
    4. It generates new versions of prompts using AI