Which statement correctly describes how per-environment configuration can be supplied without changing the template body?

Which statement correctly describes how per-environment configuration can be supplied without changing the template body?

• A. Template parameters (and optionally environment-specific ConfigMaps).
• B. Hard-coded values in the template.
• C. Environment-specific ConfigMaps.
• D. Separate templates per environment.

Answer: (A)

Per-environment configuration can be supplied by parameterizing the template and passing different values at instantiation time. Template parameters let you customize things like database endpoints, feature flags, replica counts, or image tags without touching the template’s body. You can enhance this by using environment-specific ConfigMaps that the deployed resources reference (for example, as environment variables or mounted files); you would select or supply the appropriate ConfigMap for the target environment, again without editing the template itself. This combination keeps a single template reusable across environments while delivering the necessary environment-specific data. Hard-coded values in the template require changing the template for each environment, which isn’t desired. Relying on environment-specific ConfigMaps alone can work, but without parameterizing the values you still limit how flexibly the same template can be reused. Using template parameters (with optional ConfigMaps) provides the most flexible, maintainable approach. Separate templates per environment achieves the goal but adds duplication and maintenance overhead.

Per-environment configuration can be supplied by parameterizing the template and passing different values at instantiation time. Template parameters let you customize things like database endpoints, feature flags, replica counts, or image tags without touching the template’s body. You can enhance this by using environment-specific ConfigMaps that the deployed resources reference (for example, as environment variables or mounted files); you would select or supply the appropriate ConfigMap for the target environment, again without editing the template itself. This combination keeps a single template reusable across environments while delivering the necessary environment-specific data.

Hard-coded values in the template require changing the template for each environment, which isn’t desired. Relying on environment-specific ConfigMaps alone can work, but without parameterizing the values you still limit how flexibly the same template can be reused. Using template parameters (with optional ConfigMaps) provides the most flexible, maintainable approach. Separate templates per environment achieves the goal but adds duplication and maintenance overhead.