Exam AB-100 Topic 1 Question 27 Discussion

Explanation:
Ensure consistent AI responses # Define standardized prompt templates; Support governance and version control # Store prompts in a Git repository The requirement says the shared prompt library must ensure consistent AI responses with reusable formats
. The best way to achieve that is to create standardized prompt templates .
Standardized templates help multiple business units use the same structure for:
* system instructions
* response style
* output formatting
* safety guidance
* business terminology
* escalation behavior
This is important in AI-powered business solutions because prompt variability often leads to inconsistent outputs. A shared template approach creates repeatability and reduces drift across departments.
From an enterprise AI design perspective, standardized prompt templates improve:
* response consistency
* quality control
* reusability
* onboarding speed
* compliance alignment
They also minimize administrative effort because teams do not need to invent new prompt structures from scratch.
Why "Store prompts in a Git repository" is correct
The requirement says the solution must support governance and version control while minimizing effort and cost.
A Git repository is the most appropriate answer because it provides:
* version history
* change tracking
* rollback capability
* collaboration support
* approval workflows
* auditability
This directly supports governance. It allows the organization to know:
* who changed a prompt
* what changed
* when it changed
* why it changed
That is extremely valuable for enterprise AI operations, especially when prompts influence business decisions, customer interactions, compliance behavior, or internal process automation.
Git also minimizes ongoing cost because it uses standard development and content management practices rather than requiring a separate expensive governance platform for prompt assets.
Why the other options are incorrect
Delegate department-specific prompt templates
This reduces consistency instead of improving it. Different departments creating their own templates introduces fragmentation, style drift, and governance challenges.
Maintain a prompt history
Keeping a history is useful, but it does not by itself ensure consistent reusable formats. It is more of a recordkeeping activity than a standardization mechanism.
Categorize prompts by business function
Categorization is helpful for organization and discoverability, but it does not provide version control or governance by itself.
Define standardized prompt templates for governance/version control
Standardization improves consistency, but version control specifically requires a system for tracking and managing changes. That is why Git is the better answer for the governance requirement.
Expert reasoning
A shared enterprise prompt library should usually follow this pattern:
* Consistency and reuse # standard templates
* Governance and versioning # Git-based repository
* Low cost and low admin overhead # reuse existing tooling and centralized controls