Infrastructure as Code (TF)

Question 1

How does leveraging modules to achieve code reusability and maintainability?

Answer 1

• encapsulate reusable components, such as networking setups and application stacks
• By abstracting these modules, it can reduce duplication and improve code consistency across environments

Question 2

How do workspaces help achieve code reusability and maintainability?

Answer 2

• Workspaces enables management of multiple instances of our infrastructure with minimal duplicated code

Question 3

How did you address state-related challenges?

Answer 3

1. Use a remote backend
2. Use state locking (e.g. Dynamo DB)
3. For large state files, you can us “split state” approach, breaking down the state into smaller, manageable components while maintaining cross-references

Question 4

Discuss strategies to integrate secrets management tools

Answer 4

• Used AWS Secrets Manager and Parameter store
• Automatically rotate secrets
• Mark secrets as sensitive in Terraform
• Secrets injected at runtime, not queried over the network

Question 5

Describe a scenario where you’ve used Terraform’s service-specific providers, like the AWS ECS provider, to define application-level configurations alongside infrastructure provisioning?

Answer 5

• In a containerized application deployment, we used the AWS ECS provider within Terraform to define the application’s task definitions, services, and load balancers alongside the infrastructure components.
• This integrated approach ensured that both infrastructure and application configuration were versioned and deployed together, minimizing inconsistencies.

Question 6

How would you use Infrastructure as Code (IaC) validation and policy enforcement?

Answer 6

1. enforce compliance and naming conventions
2. validate security group configurations
3. catch errors before deployment

Question 7

When designing a Terraform project structure, what are the key considerations you take into account to ensure maintainability and scalability?

Answer 7

• prioritize modularization to promote reusability and easier maintenance.
• each module encapsulates a specific piece of infrastructure
• use variables and outputs to abstract configuration details and create clear interfaces for module usage
• structure the project with directories for modules, environments, and global configurations

Question 8

How do you structure your project to effectively manage environment-specific configurations while minimizing duplication and ensuring consistent infrastructure provisioning across environments?

Answer 8

• adopt a flexible approach to manage environments
• use workspaces or separate directories for each environment
• allow isolated state files and configuration files per environment if using directories
• environment-specific variables are managed in separate files or using Terraform’s variable overrides
• leverage Terraform’s ability to use module inheritance
• define shared modules in the root directory and use them across environments with environment-specific variable values

Question 9

Discuss your approach to organizing and storing Terraform state files?

Answer 9

• use remote backends like Amazon S3 or HashiCorp Consul to store state files
• for isolation, create separate S3 buckets or Consul namespaces for each environment
• for collaborative settings, I emphasize the use of state locking mechanisms