Study/Devops-exercises
1
0
Fork 0
mirror of https://github.com/bregman-arie/devops-exercises.git synced 2026-02-04 23:59:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

added a variable question (#10585)

Browse Source 
* added a variable question

* added a disaster recovery question in AWS

* added a backend question

* added questions on manual config vs IaC

* Update topics/terraform/README.md

Co-authored-by: andrzejsydor <andrzejsydor@users.noreply.github.com>

---------

Co-authored-by: andrzejsydor <andrzejsydor@users.noreply.github.com>
This commit is contained in:
Shubham Machal 2025-08-07 10:27:04 -07:00 committed by GitHub
parent 5cfd044135
commit be401b71b5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 35 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
topics/aws/README.md
View File

@ -1688,6 +1688,11 @@ True
A transport solution which was designed for transferring large amounts of data (petabyte-scale) into and out the AWS cloud.
</b></details>
<details>
<summary> How can a company ensure their web application continues to operate if it becomes unavailable in its current single region?</summary><br><b>
Deploy the application in multiple Regions. Use Amazon Route 53 DNS health checks to route traffic to a healthy Region
</b></details>
### ELB
<details>

30
topics/terraform/README.md
View File

@ -75,6 +75,17 @@
-
</b></details>
<details>
<summary>What is one reason why manual processes can be helpful?</summary><br><b>
For learning a platform when first starting out
</b></details>
<details>
<summary>Why is it advisable to avoid using manual processes when creating infrastructure at scale?</summary>
Manual processes for creating infrastructure are slow because they require human intervention for each step, which delays deployment. They are error-prone since manual configuration increases the risk of mistakes and inconsistencies. Additionally, these processes are not easily repeatable, making it difficult to ensure the same infrastructure setup across different environments—unlike Infrastructure as Code (IaC), which automates and standardizes deployments.
</b></details>
<details>
<summary>What are some of Terraform features?</summary><br><b>
@ -402,6 +413,18 @@ If no value given, user will be prompted to provide one.
Using the syntax `var.<VAR_NAME>`
</b></details>
<details>
[Question] You are configuring a variable for your Terraform configuration. Which arguments are required when configuring a `variable` block? 1. `type` and `description` 2. There are no required arguments 3. `type` 4. `type`, `description` and `default`
[Answer]</b> 2. There are no required arguments
In Terraform, when declaring a variable block, there are no mandatory arguments. You can create a variable with an empty block like:
variable "example" {}
While `type`, `description`, and `default` are commonly used, they're all optional. The `type` argument helps with validation, `description` documents the variable's purpose, and `default` provides a fallback value if none is specified.
</details>
<details>
<summary>What is the effect of setting variable as "sensitive"?</summary><br><b>
@ -947,6 +970,13 @@ You can use it the following syntax `data.terraform_remote_state.<NAME>.outputs.
</b></details>
<details>
<summary>How does a remote state backend improve collaboration for a Terraform project?</summary><br><b>
By storing the state file in a shared location enabling multiple people or processes to work with the same state.
A remote state backend improves collaboration on Terraform projects by addressing the core challenge of sharing infrastructure state. When a team works on infrastructure, everyone needs access to the current state to safely make changes.
</b></details>
#### Workspaces
<details>