Infrastructure-as-Code Operational Aspects for CCNP Enterprise

The question asks for operational aspects of Infrastructure-as-Code (IaC). IaC is the practice of managing and provisioning computing infrastructure through machine-readable definition files rather than physical hardware configuration or interactive configuration tools. The core operational pillars of IaC revolve around version control, automation, and programmatic interaction.

Option B, source code management repository, is a fundamental operational aspect. IaC treats infrastructure definitions as code, which must be stored in version-controlled repositories (like Git) to enable tracking, collaboration, rollback, and auditing. This is the "source of truth" for the infrastructure state.

Option E, automated workflows, is the other key operational aspect. IaC integrates with CI/CD pipelines to automatically validate, test, and deploy infrastructure changes. This automation ensures consistency, reduces human error, and speeds up deployment, which are primary benefits of using IaC.

Option A, telemetry and monitoring, while important for network operations, is typically a separate concern handled by observability tools. IaC might configure these tools, but monitoring itself is not an intrinsic operational aspect of the IaC methodology; it is a downstream effect or a separate domain.

Option C, automatic trouble ticketing, is a service management process, often part of ITIL or similar frameworks, and is not a direct operational component of IaC.

Option D, API for programmatic control, is a mechanism used by IaC tools to interact with cloud providers or network devices, but the API itself is a technical interface, not an operational aspect of the IaC lifecycle in the same way that source control and automation workflows are. However, between B and E, these represent the structural (storage/versioning) and procedural (automation/workflow) pillars of IaC operations most commonly cited in certification contexts.