YouTube Instagram TikTok How it works FAQ

The fastest way to turn talking videos into clean, searchable text. Free, private and no account required.

About

Built by Rishav Raj with one goal: free transcripts for everyone.

rishav@yttotranscript.com

Transcribe

YouTube to text
YouTube with timestamps
Instagram Reels
TikTok videos

Learn

How it works
FAQ
YouTube transcripts guide

More

Chrome extension
Contact
Privacy policy
Terms of service

© 2026 YTtoTranscript. Made for creators & researchers.

Not affiliated with YouTube, Instagram or TikTok. Respect creators’ copyright.

Terraform | CCNA 200-301 Day 63 (part 2) — Transcript · YTtoTranscript

Home/Transcripts/YouTube

YouTube Transcript

Terraform | CCNA 200-301 Day 63 (part 2)

Jeremy's IT Lab · 3,160 words · 16 min read · EN-ORIG

Watch on YouTube

Share X LinkedIn WhatsApp

Below is the complete, readable transcript of Terraform | CCNA 200-301 Day 63 (part 2) by Jeremy's IT Lab on YouTube. Read the full text, copy any part you need, or generate a transcript for any video with our free tool.

hi from Tokyo Japan and welcome to Jeremy's it lab in this video we are covering another recent addition to the CCNA exam terraform the exam blueprint previously listed anible puppet and Chef as the configuration management tools you need to know for the exam Cisco recently changed that to anible and terraform however I'm keeping puppet and

Chef in the course for two reasons first notice the wording of the new exam topic recognize the capabilities of configuration management mechanisms such as anible and terraform for me the words such as imply that there could be others on the exam second puppet and shef help illustrate key Concepts like comparing the agentless architecture of anible and

terraform to the agent-based architecture of puppet and Chef so instead of modifying the previous video I'm adding this new one to focus on form before we get started let me take a minute to shill my books acing the CC exam volumes 1 and two these books cover everything on the latest version of the

CCNA exam including the topics of this video the very final chapter chapter 25 of volume 2 focuses on ansible and terraform and also includes a bit about puppet and Chef I always recommend using books in combination with a video course so if you want to get my books check out the links on the screen now to buy them

directly from the publisher or find them on Amazon now let's get started so what are we going to cover in this video of course the focus is on terraform but I'll take the opportunity to introduce a few new Concepts specifically we'll talk about the concept of infrastructure as code IAC terraform and the other tools we've

Transcribe another video

Paste any YouTube, Instagram or TikTok link to get a free transcript.

Free · No sign-up · Unlimited

Add to Chrome — transcribe in one click

covered are examples of IAC then we'll compare infrastructure provisioning and configuration management whereas anible is primarily used for for configuration management terraform leads towards provisioning we'll then cover the concepts of mutable and immutable infrastructure and procedural versus declarative approaches finally we'll shift our Focus to terraform itself and cover its Basics okay let's

begin first let's look at the concept of infrastructure as code actually we've already covered it I just didn't use the specific term in the last video infrastructure as code IAC is is the practice of provisioning and managing infrastructure such as servers networks and Cloud resources using machine readable configuration files code instead of manual configuration via CLI

or GUI that probably sounds familiar because anible puppet and Chef are examples of IAC configuration management tools for example anible manages device configurations using several files that are used by the control node we covered these in the previous video anible uses Playbook inventory template and variable files anible runs on the control node

and uses these files to manage the infrastructure instead of configuring the devices via the CLI or GUI their configurations are managed via these code files hence the term infrastructure as code terraform on the other hand is an IAC based provisioning tool that automates the creation of infrastructure resources in the next slide I'll click

clarify the difference between configuration management and provisioning but terraform is primarily used for provisioning so to summarize infrastructure as code automates infrastructure deployment and management ensuring consistency scalability and repeatability basically the various benefits of automation that we covered in previous videos so I mentioned that anible puppet and Chef are primarily configuration management tools whereas terraform is

primarily a provisioning tool let's clarify what the difference is first what is configuration management tools like anible puppet and Chef manage existing infrastructure by installing software configuring settings and maintaining system State this ensures consistency by applying and enforcing configurations across multiple devices again these are the benefits of anible puppet and Chef that I covered in the

previous video as for infrastructure provisioning it creates modifies and deletes infrastructure resources such as servers and network infrastructure for example creating virtual servers and routers on a cloud platform like AWS but the focus is on initial setup rather than ongoing configuration management to summarize configuration management tools work on already existing systems whereas provisioning

tools build infrastructure from scratch of course these tools can be used together for example terraform a provisioning tool and anible a configuration management tool often work as a pair terraform Provisions infrastructure creating VMS Network infrastructure storage and other resources while anible provides ongoing configuration and management maintaining those systems with all of that said both

terraform and anible have some overlap each can perform both provisioning and configuration management to some extent but their strengths are different so they're often used together one major difference between infrastructure provisioning and management tools is the approach they take with the infrastructure is the infrastructure mutable or immutable configuration management tools typically use a mutable infrastructure

approach this means that infrastructure can be modified after deployment such as applying updates patches or configuration changes in other other words changes are made in place meaning existing resources are updated rather than replaced this is just like when you manually modify a device's configuration in the CLI so when using a mutable approach if

you want to update the config of this VM anible or a similar tool would simply update the config while leaving the VM itself in place only the relevant settings are changed so what's the alternative to mutable infrastructure provisioning tools like terraform typically employ an immutable infrastructure approach this means that infrastructure cannot be changed after

deployment so any changes you make involve replacing the previous resource with a new one if you want to update the configuration of this VM terraform or a similar tool would have to create an updated instance of the VM with the configuration changes applied and then destroy the old instance one benefit of this approach is

that there is no configuration drift each deployment starts from a fresh predefined State there's no opportunity for individual changes to accumulate with each configuration configuration drift isn't a major issue when anible or other mutable infrastructure tools are properly managed but terraforms immutable approach virtually eliminates the risk altogether the final concept we'll cover

before focusing on terraform itself is the difference between a procedural and declarative approach some tools take a procedural approach to managing infrastructure also called an imperative approach this means that the tool follows explicit steps in a specific order to achieve the desired outcome so the user the engineer using the tool must Define each specific action in the

correct order to configure the infrastructure this provides greater control than the declarative approach will'll cover next but is more demanding on the user they have to know exactly which steps are required to achieve their desired end result and in which order those steps should be executed then there is the declarative approach which defines the desired end

State instead of the specific steps the tool itself such as terraform figures out the steps needed to achieve the goal this makes it easier to maintain and ensure consistency across deployments because the user doesn't have to worry about ordering individual commands and configurations on each platform they only have to think about defining what

they want the final result to be so to summarize a procedural approach focuses on how to make changes with explicit steps for example when configuring a new router configure the router's host name with host name R1 configure the IP address of g01 with the IP address command enable the interface with no shutdown and so on these are the

specific configurations needed on a Cisco router and the steps would be different different if it was a juniper router for example a declarative approach on the other hand focuses on what the final State Should Be You Can Tell terraform create a router named R1 with IP address 192.168.1.1 24 on its g01 interface

ensuring the interface is enabled terraform should then figure out the necessary steps to achieve that end state so I've mentioned that terraform uses a declarative approach but you're probably wondering about the others here's a table I've categorized anible and Chef as procedural but it's worth noting that they do have some declarative elements as well especially

anible people who use anible a lot might get angry at me for categorizing anible as procedural but red hat the company that owns and develops anible also says it is procedural so for your CCNA studies I'd say it's best to consider anible a procedural tool meanwhile terraform and puppet use a Clara of

approach allowing you to define the desired end State and let the tool figure out the rest for you finally let's move on to terraform which is an open source IAC tool developed by Hashi Corp an American company that was acquired by IBM in 2025 as I've mentioned a few times it is primarily a provisioning tool focused on

deploying infrastructure resources on various cloud and on-prem Platforms in terraform these platforms are called providers and include AWS Azure gcp kubernetes and many more it supports over 1,000 different providers for CCNA students this includes Integrations with Cisco platforms like Catalyst Center ACI which is application Centric infrastructure Cisco's data center sdn solution and iOS

XE which is the type of iOS you'll find on Modern Cisco devices like Catalyst switches like anable terraform uses a push model and is agentless it doesn't require a software agent on infrastructure it Provisions or manages okay now let's see how terraform actually works at the core of terraform is terraform core this is the main

terraform software typically running on a Linux server that processes configurations and interacts with providers an engineer creates terraform configuration files which specify the desired end state in a declar ative fashion it's up to terraform core to take that desired end State and deploy the necessary infrastructure on the appropriate provider or providers such

as deploying Cloud resources on AWS it does this via each provider's apis and one more key element is the state file which terraform uses to track the state of the deployed infrastructure by comparing the current state of the infrastructure to the desired end State defined in the configuration files terraform can identify which actions it

needs to take and in which order to achieve the desired result to summarize these are terraforms four key components all working together to provision and manage infrastructure terraform core the core software developed by hashicorp configuration files which an engineer creates to define the desired end state of the infrastructure the state file which

tracks the current state of the deployed infrastructure and and the providers the platforms on which the infrastructure is deployed let's cover a few more key points about terraform the basic terraform workflow consists of three main steps the first is write in which you define the desired end state of your infrastructure resources in configuration

files the second step is plan where terraform analyzes your configuration files and shows you exactly what changes will be made this lets you to review and confirm the changes before applying them and the third step is apply where terraform executes the plan to provision and manage the infrastructure resources that's basically how it

works if you think back to ansible hopefully you remember that anible itself is written in Python while its playbooks are written in yaml so what about terraform while terraform core is written in go the configuration files that Define the desired end state are written in Hashi Corp configuration language HCL HCL is an example of a domain

specific language DSL which is specialized for a particular purpose like puppets DSL mentioned in the previous video since dsls are designed for specific tasks they make complex operations simpler and they require less effort compared to general purpose languages like python or go the downside is that HCL is another thing you have to

learn specifically to use Tera form but it's relatively simple compared to learning a full programming language so the key points to remember here are the three steps of the terraform workflow write plan and apply and also remember that terraform core is written in go while the configuration files you make are written in Hashi Corp

configuration language HCL which is a domain specific language okay those are the basics of terraform now here's a one slide summary before we move on to the quiz infrastructure as code is the practice of provisioning and managing infrastructure using machine readable configuration files instead of manual configuration anible puppet chef and terraform are all examples of IAC tools

but not all IAC tools are used for the exact same purpose configuration management tools like anible puppet and Chef focus on managing existing infrastructure doing things like installing software configuring settings and generally maintaining the state of your systems infrastructure provisioning tools like terraform on the other hand focus on creating modifying and deleting

infrastructure resources that doesn't mean that anible can't be used to provision resources or terraform can't be used to make configuration changes it's just that each tool is better fit for a different purpose we then covered mutable infrastructure which means that the infrastructure can be modified after deployment and immutable infrastructure meaning that it cannot be changed after

deployment any changes involve replacing the previous resource with a new updated version and then deleting the old one provisioning tools like terraform use an immutable approach whereas management tools like anible use a mutable approach to infrastructure we then compared the procedural and declarative approaches a procedural also called imperative approach follows explicit steps steps in

a specific order to achieve the desired outcome and these steps must be specified by the engineer using the tool a declarative approach defines the desired end State and the IAC tool such as terraform figures out the steps needed to achieve that goal and in which order they should be executed okay finally we looked at

terraform itself it's an open- Source IAC tool developed by Hashi Corp it's primarily a provisioning tool used for deploying infrastructure on providers like AWS Azure gcp kubernetes Etc terraform interacts with these providers via their apis like anible it uses a push model and is agentless its main components are terraform core the configuration files

where you specify the desired end State the state file that tracks the current state of the infrastructure and the providers the basic workflow consists of three main steps rate plan and apply you could also add a fourth step there destroy in which you delete the resources after they are no longer needed but these three are considered

the main steps terraform core is written in go and the configuration files are written in Hashi Corp configuration language which is a domain specific language all right that's what we covered in this video just a very high level overview of terraform but as long as you know these Basics you should be ready for the CCNA exam now let's do a

short quiz to test your understanding here's quiz question one which of the following are characteristics of terraform select two pause the video now to think about your answers okay the answers are B declarative and C immutable infrastructure terraform uses a declarative approach in which you specify the desired end State and terraform takes takes care of the rest

for you it also uses immutable infrastructure where a particular resource can't be changed after provisioning to change a resource terraform will deploy a new version of the resource and then delete the old one instead okay next question here's question two what are the three main steps of the terraform workflow pause the video now to think

about your answer okay the answer is D WR plan apply in the right step you define the desired state of your infrastructure in configuration files in the plan step you verify the changes that will be executed before applying them and then in apply terraform applies whatever changes necessary to bring the infrastructure in

line with the desired State now let's do one more question here's quiz question three which of the following IAC tools are focused on configuration management select three pause the video now to think about your answers okay the answers are a c and d anible chef and puppet are primarily used for configuration management

whereas terraform is a provisioning tool to take advantage of the strengths of each it's fairly common to use a combination such as terraform and anible these tools aren't exclusive and can can be used together okay that's all for this video we covered some additional concepts related to infrastructure as code that weren't covered in the previous video

and then focused on the basics of terraform a very popular IAC provisioning tool for the CCNA exam I recommend knowing the basics of terraform introduced in this video you should also be able to compare and contrast it with the other tools we covered in the previous video anible puppet and Chef I hope this video was

helpful thanks for watching before finishing this video let me thank my jcmp level channel members who support me through YouTube channel membership to become a member please click the join button under the video thanks to yonathan MAA George Gustavo maedo Marcel Lord dros Hera Zak Shaw mayor Salman Mark Jackson bold c1u Gerald Guam Hector Hernandez arpad conz

F feet oad Daniel Brown Jose Alvarez jusan yavuz Samuel Tavarez Kevin Hayes Brian Grant Gori gev Addison Pereira madm Mark 50484 Alexander Straton dmj 2 Steve Cox Jasper Yim Pedro Hartman tricky Mickey 123456 Jefferson steel Flex toxic cenan cinar Wilmer Romero Daniel Andrade dragos George Philip yovanovich Sunny igu hello bpdu edifer mikal chapski

Haman jabal Puri darush D Juan Morales Gonzalo Nicolas doomed Soul Julio Maya egreso Hashem Roda Anand Aban Clyde Muro bindo orando Flores Adrien Martinez gg7 Ray Enriquez Tobe hedin MDS Electro naria G Gant Henrietta SAU yuk shika Uma Shankar Sharma Alara beler sebz James Corley Alexi usov seram gasam excelus Captain Flamingo to be like our

superheroes muhamad Balta Tazo ganad opero Muhammad Mateo Falcone omole Seline genre be good Zack Ross I'm me 87 cind on KD Marco Christ ready Adventures limited DB Foreigner and Manuel morote sorry if I pronounced your name incorrectly but thank you so much for your support thanks to you and my other supporters I am able to make these

videos and release them for free on YouTube so I really appreciate the support another great way to support the channel is to like the video leave a comment subscribe and most importantly share this video with others so if this video was helpful I'd appreciate it if you did any of those thanks for watching

[Music]