AgentforceArchitect (Hardest)cicdversioningmetadata
Architect version control and CI/CD for agent topic and action changes
Real World Scenario
Multiple teams edit same service agent topics in production; breaking change removed escalation action during peak season without rollback path.
Expected Answer
• Treat agent config as metadata in git with PR review
• Environment promotion dev → UAT → prod with automated regression tests
• Semantic versioning on agent bundles with release notes
• Feature flag new topics dark launch before customer exposure
• Rollback runbook restoring prior metadata package in minutes
• Ownership matrix per topic and action
• Synthetic conversation tests in CI blocking deploy on failure
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Treat agent config as metadata in git with PR review Also consider: Environment promotion dev → UAT → prod with automated regression tests In practice: Semantic versioning on agent bundles with release notes Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Agents in prod without CI/CD is editing live call center scripts without rehearsal — unacceptable at scale.