Answer: The main goal was to build a reusable configuration workflow using Jinja2 templates, YAML data files, and validation checks before deployment.
Answer: Jinja2 made it possible to keep one reusable template and render different outputs for development and production from separate data files.
Answer: Environment-specific values were stored in separate YAML files, then injected into the templates during generation.
Answer: It loaded YAML input, rendered Jinja2 templates, and wrote the generated configuration files to the configs directory.
Answer: It validated generated YAML files against JSON schema and performed basic syntax checks for Nginx configuration.
Answer: It helped catch missing or malformed configuration values before those settings could be deployed or used downstream.
Answer: It proved that bad input could still generate output, but the validator correctly identified the missing required values.
Answer: The lab used a basic validator that checked brace balance, required blocks, and semicolon placement.
Answer: It reflects template-driven configuration management used in deployment automation and infrastructure-as-code workflows.
Answer: I verified that the modules loaded, files were generated, expected values existed, and the validation commands returned the correct exit status.