Fifth Flashcards Preview

P211A000N02F > Fifth > Flashcards

Flashcards in Fifth Deck (4)
Loading flashcards...
1

What are the main benefits of a multi-cloud deployment?

A. There are no benefits, multi-cloud just increase the billing and also add complexity to the infrastructure management
B. Multi-cloud deployment allows us to create the same infrastructure in multiple regions or multi-cloud providers, having a fault tolerance application in case of a region or cloud provider is failing
C. Have multiple applications distributed in geographically distributed to reduce latency for your customers
D. B and C

B. Multi-cloud deployment allows us to create the same infrastructure in multiple regions or multi-cloud providers, having a fault tolerance application in case of a region or cloud provider is failing

With Terraform, we are to deploy the same code in different regions for the same cloud providers increasing the fault tolerance of the infrastructure.

Option A is incorrect because there are multiple benefits like fault tolerance. Also, the infrastructure management can be easily addressed with Terraform managing multiple providers.

Option C is incorrect because multi-cloud deployments don’t mean that you have your applications in multiple regions, means you have your infrastructure deployed with different cloud providers

Option D is incorrect as C is not properly correct

https://www.terraform.io/intro/use-cases.html#multi-cloud-deployment

2

What means that Terraform is cloud-agnostic?

A. You can deploy your infrastructure into different cloud providers using the same code.
B. You can deploy your infrastructure into different cloud providers using the same language and different providers
C. You can create infrastructure into different cloud providers using the same language without managing dependencies between them
D. Terraform is not cloud-agnostic

B. You can deploy your infrastructure into different cloud providers using the same language and different providers

You can create and deploy your infrastructure using HCL creating the resources by the providers definition.

Answer A is incorrect. You can’t deploy using the same code, but using the same language yes. You must adapt your code to the providers definition and configuration.

Answer C is incorrect as you can manage dependencies between resources of different cloud providers.

Answer D is incorrect because one of the main advantages of Terraform is cloud-agnostic

https://www.terraform.io/intro/use-cases.html

3

What are the main benefits to have a Terraform State?

A. Mapping to the real world
B. Dependencies between resources
C. Synchronization
D. All the above

D. All the above

Mapping with the real world. When we create a resource in a cloud provider, Terraform needs to identify that this resource is mapped to our code.

Terraform uses metadata information to manage dependencies between resources. For example, when you delete a resource, Terraform uses this metadata to know in which order this resource must be deleted.

When multiple users are working on the same code, the state must be share to be sync with the infrastructure deployment.

A, B, and C are incorrect. Although individually are correct, the best and most complete answer is D

https://www.terraform.io/docs/language/state/purpose.html

4

Where is the Terraform State written by default?

A. In an Amazon S3 Bucket.
B. In the local directory where you are planning and deploying your infrastructure
C. $WORKDIRECTORY/.terraform/states/
D. Terraform doesn’t create a Terraform State by default

B. In the local directory where you are planning and deploying your infrastructure right

If you don’t specify a backend configuration for your Terraform State, this will be created by default on the directory where you are working called terraform.tfstate

Option A is incorrect because you have to configure this to use Amazon S3 as the backend, but Amazon S3 is not configured by default

Option C is incorrect because if you want Terraform to write your state on this directory, you have to configure this in your backend

Option D is incorrect because Terraform always will create a terraform state when you initialize doing a terraform init

https://learn.hashicorp.com/tutorials/terraform/aws-build?in=terraform/aws-get-started