Q: Environment configuration details can be integrated during build time.

A True
B False

Share this MCQ

Answer: A

Explanation:

✅ True

Explanation:

Environment configuration details can be integrated during build time, but it is generally not recommended for best practices.

At build time, configurations (such as database connections, API keys, or feature flags) can be baked into the build artifacts, but this approach has limitations:

Requires a separate build for each environment (e.g., Dev, QA, Prod).
Reduces flexibility in deploying the same artifact across multiple environments.
Can expose sensitive information if not handled securely.

Best Practice:

Instead of integrating configurations at build time, it's better to:

Use external configuration files or environment variables.
Store secrets securely in vaults (e.g., Azure Key Vault, AWS Secrets Manager).
Keep builds environment-agnostic to support Continuous Deployment (CD).

Thus, while True, it's not the best practice for modern DevOps workflows. ✅

Q: Environment configuration details can be integrated during build time.

Explanation:

Best Practice:

Report Question