Untitled Quiz

KODE KLOUD Terraform Certification Details

• Duration: 60 minutes
• Cost: $70.50 USD
• Validity: 2 years
• Question Type: Multiple choice, multiple options, true/false
• Number of Questions: ~57
• Proctoring: Online proctored
• Virtual Machines: No VMs
• Browser: PSI Secure Browser
• Additional Equipment: No additional monitors or headphones
• Equipment Requirements: Webcam, speakers, and microphone turned on; quiet, well-lit, and clean room
• Registration: https://www.hashicorp.com/certification/terraform-associate

Terraform Cloud

• Connects Users: to physical machines, VMware, Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure.
• Uses: .tf files and terraform.tfstate files.
• Version Control: Terraform Cloud uses version control with tools like GitHub.
• Multiple Cloud Providers: Supports multiple cloud providers (e.g., AWS, GCP, Azure).
• Shared State: Provides a consistent and reliable environment through shared state.
• Ul Interface: User-friendly interface
• Secret Management: Secure management of secrets
• Access Controls: Access controls are managed via the interface.
• Private Registry: Supports private registries.
• Policy Controls: Implementation of policy controls within the interface.
• Different Versions: 1.0 and 0.12 versions are shown representing potential use cases.

Introduction to Terraform Cloud

• It enables a centralized management system for infrastructure resources.
• HashiCorp Terraform Cloud is a service running in the cloud which manages infrastucture code in a consistent and reliable environment.

Types of IAC Tools

• Configuration Management: Tools like Ansible, Puppet, SaltStack designed to install and manage software. They maintain a standard structure, leverage version control and are idempotent.
• Server Templating: Tools like Packer, Docker, Vagrant pre-install software and dependencies and use immutable infrastructure (e.g.) VM or Docker images.
• Provisioning Tools: Tools like HashiCorp Terraform, CloudFormation are used to deploy immutable infrastructure resources (like servers, databases, network components), and function across multiple providers.

Installing Terraform & HCL Basics

• Terraform Installation: Download and install for different operating systems (macOS, Linux, Windows, FreeBSD, OpenBSD, Solaris) using the appropriate wget commands, unzip, and mv to the specified directory to properly install Terraform.
• HCL Basics: HCL (HashiCorp Configuration Language) is used as a declarative language for defining infrastructure as code. Code examples are provided in local.tf for defining the file structure and content.

Terraform Basic Commands

• terraform init: Initializes the Terraform environment
• terraform plan: Generates an execution plan to show the upcoming changes to your infrastructure
• terraform apply: Applies the changes from terraform plan
• terraform destroy: Destroys the resources defined within your infrastructure
• terraform show: Displays the configuration of your infrastructure
• terraform fmt: Formats your infrastructure code within your configuration files for easier readability.

Terraform State & Variables

• Terraform state persists the infrastructure configuration using a state file.
• Variables in Terraform can be defined and used.
• Precedence of variables means some can take precedence over others during application.
• Variables can be defined in different files and provide defaults for use.

Terraform Providers

• Accessing cloud resources.
• Different types of providers.
• Official, verified & community providers.

Terraform Modules

• Reusable configurations; avoid code repetition by using pre-built configs.
• The main.tf file acts as the entry point for configuration when using modules.

Terraform Aliases

• Can be used to reduce typing. Creating short names for larger inputs.
• Defined in provider.tf file; can use default AWS cloud attributes for example.

Terraform Resources

• 'resource' keyword denotes a type of actionable object; creates, updates, or destroys infrastructure.
• Example: aws instance, aws key pair, aws security group.

Terraform Data Sources

• 'data' keyword denotes a type of non-actionable object—acts as a data source and only reads from existing structure within an infrastructure. No changes are performed. Example: aws key-pair.

Count and For-Each

• count: A resource can be deployed multiple times based on set sizes— useful for deploying multiple instances of identical resources within an infrastructure.
• for_each: A resource can be deployed multiple times (dynamically) based on an item count (such as items within a list or map)

Terraform Output

• Used to show outputs—for example, outputs of a previously run configuration.

Dynamic Blocks

• Create multiple resources using a variable containing a map or list of values
• Replaces parts of a resource with variable values

Terraform Workspaces

• Create isolated instances of terraform.
• Separate environments with isolated configurations.

Terraform Provisioners

• Used to execute commands on the provisioned resources— useful for configuring remote environments (e.g., installing packages).

Terraform Taint

• Marks a resource as tainted (meaning in need of re-creation).
• Used to force a resource to be re-provisioned, such as when changes have been made and are not reflected in the configuration.

Terraform Import

• Imports a resource from an existing infrastructure into your Terraform state.

Terraform State

• Stores Terraform's configuration and relationships between resources in a state file.
• Remote backend stores the state in a cloud environment while local state is stored locally (in a file).

Debugging

• Output useful logging to view and debug Terraform execution issues.

Terraform Aliases

• Provide shorthand names to reduce typing for commands or large configuration entries.

Terraform Commands

Terraform Lifecycle Rules

• Specify when to create, update, or destroy resources. This is useful when dealing with resources in another stage being dependent on previous resources.