[2024年06月06日] 究極のTerraform-Associate-003準備ガイド!無料最新のHashiCorp練習テスト問題集 [Q74-Q91]

Share

[2024年06月06日] 究極のTerraform-Associate-003準備ガイド!無料最新のHashiCorp練習テスト問題集

今すぐゲットせよ!高評価HashiCorp Terraform-Associate-003試験問題集


HashiCorp Terraform-Associate-003 認定試験の出題範囲:

トピック出題範囲
トピック 1
  • Read, generate, and modify configuration
  • Handle backend and cloud integration authentication methods
トピック 2
  • Create and differentiate resource and data configuration
  • Describe how Terraform finds and fetches providers
トピック 3
  • Describe how Terraform Cloud enables collaboration and governance
  • Describe secure secret injection best practice
トピック 4
  • Differentiate remote state back end options
  • Understand the use of collection and structural types
トピック 5
  • Interact with module inputs and outputs
  • Describe backend block and cloud integration in configuration
トピック 6
  • Use terraform state to view Terraform state
  • Apply formatting and style adjustments to a configuration
トピック 7
  • Understand infrastructure as code (IaC) concepts
  • Generate and review an execution plan for Terraform

 

質問 # 74
You have a Terraform configuration that defines a single virtual machine with no references to it, You have run terraform apply to create the resource, and then removed the resource definition from your Terraform configuration file.
What will happen you run terraform apply in the working directory again?

  • A. Nothing
  • B. Terraform will remove the virtual machine from the state file, but the resource will still exist
  • C. Terraform will error
  • D. Terraform will destroy the virtual machine

正解:D

解説:
This is what will happen if you run terraform apply in the working directory again, after removing the resource definition from your Terraform configuration file. Terraform will detect that there is a resource in the state file that is not present in the configuration file, and will assume that you want to delete it.


質問 # 75
Which of these ate features of Terraform Cloud? Choose two correct answers.

  • A. A web-based user interface (Ul)
  • B. Automated infrastructure deployment visualization
  • C. Automatic backups
  • D. Remote state storage

正解:A、D

解説:
These are features of Terraform Cloud, which is a hosted service that provides a web-based UI, remote state storage, remote operations, collaboration features, and more for managing your Terraform infrastructure.


質問 # 76
What is the name of the default file where Terraform stores the state?
Type your answer in the field provided. The text field is not case-sensitive and all variations of the correct answer are accepted.

正解:

解説:
Terraformtfstate
Explanation:
The name of the default file where Terraform stores the state is terraform.tfstate. This file contains a JSON representation of the current state of the infrastructure managed by Terraform. Terraform uses this file to track the metadata and attributes of the resources, and to plan and apply changes. By default, Terraform stores the state file locally in the same directory as the configuration files, but it can also be configured to store the state remotely in a backend. Reference = [Terraform State], [State File Format]


質問 # 77
How can a ticket-based system slow down infrastructure provisioning and limit the ability to scale? Choose two correct answers.

  • A. The more resources your organization needs, the more tickets your infrastructure team has to process
  • B. Users can access catalog of approved resources from drop down list in a request form
  • C. End-users have to request infrastructure changes
  • D. Ticket based systems generate a full audit trail of the request and fulfillment process

正解:C

解説:
Explanation
These are some of the ways that a ticket-based system can slow down infrastructure provisioning and limit the ability to scale, as they introduce delays, bottlenecks, and manual interventions in the process of creating and modifying infrastructure.


質問 # 78
You modified your Terraform configuration and run Terraform plan to review the changes. Simultaneously, your teammate manually modified the infrastructure component you are working on. Since you already ran terraform plan locally, the execution plan for terraform apply will be the same.

  • A. False
  • B. True

正解:A

解説:
The execution plan for terraform apply will not be the same as the one you ran locally with terraform plan, if your teammate manually modified the infrastructure component you are working on. This is because Terraform will refresh the state file before applying any changes, and will detect any differences between the state and the real resources.


質問 # 79
How is terraform import run?

  • A. As a part of terraform init
  • B. As a part of terraform plan
  • C. By an explicit call
  • D. As a part of terraform refresh
  • E. All of the above

正解:C

解説:
The terraform import command is not part of any other Terraform workflow. It must be explicitly invoked by the user with the appropriate arguments, such as the resource address and the ID of the existing infrastructure to import. Reference = [Importing Infrastructure]


質問 # 80
How does Terraform manage most dependencies between resources?

  • A. By defining dependencies as modules and including them in a particular order
  • B. The order that resources appear in Terraform configuration indicates dependencies
  • C. Using the depends_on parameter
  • D. Terraform will automatically manage most resource dependencies

正解:D

解説:
Explanation
This is how Terraform manages most dependencies between resources, by using the references between them in the configuration files. For example, if resource A depends on resource B, Terraform will create resource B first and then pass its attributes to resource A.


質問 # 81
Which of the following does terraform apply change after you approve the execution plan? (Choose two.)

  • A. The .terraform directory
  • B. Terraform code
  • C. State file
  • D. Cloud infrastructure Most Voted
  • E. The execution plan

正解:C、D

解説:
The terraform apply command changes both the cloud infrastructure and the state file after you approve the execution plan. The command creates, updates, or destroys the infrastructure resources to match the configuration. It also updates the state file to reflect the new state of the infrastructure. The .terraform directory, the execution plan, and the Terraform code are not changed by the terraform apply command. Reference = Command: apply and Purpose of Terraform State


質問 # 82
What is a key benefit of the Terraform state file?

  • A. A state file is a source of truth for resources provisioned with Terraform
  • B. A state file is the desired state expressed by the Terraform code files
  • C. A state file is a source of truth for resources provisioned with a public cloud console
  • D. A state file can schedule recurring infrastructure tasks

正解:A

解説:
Explanation
This is a key benefit of the Terraform state file, as it stores and tracks the metadata and attributes of the resources that are managed by Terraform, and allows Terraform to compare the current state with the desired state expressed by your configuration files.


質問 # 83
Which of these ate features of Terraform Cloud? Choose two correct answers.

  • A. A web-based user interface (Ul)
  • B. Automated infrastructure deployment visualization
  • C. Automatic backups
  • D. Remote state storage

正解:A、D

解説:
Explanation
These are features of Terraform Cloud, which is a hosted service that provides a web-based UI, remote state storage, remote operations, collaboration features, and more for managing your Terraform infrastructure.


質問 # 84
Terraform providers are part of the Terraform core binary.

  • A. False
  • B. True

正解:A

解説:
Explanation
Terraform providers are not part of the Terraform core binary. Providers are distributed separately from Terraform itself and have their own release cadence and version numbers. Providers are plugins that Terraform uses to interact with various APIs, such as cloud providers, SaaS providers, and other services. You can find and install providers from the Terraform Registry, which hosts providers for most major infrastructure platforms. You can also load providers from a local mirror or cache, or develop your own custom providers.
To use a provider in your Terraform configuration, you need to declare it in the provider requirements block and optionally configure its settings in the provider block. References = : Providers - Configuration Language | Terraform : Terraform Registry - Providers Overview | Terraform


質問 # 85
What does Terraform not reference when running a terraform apply -refresh-only ?

  • A. Cloud provider
  • B. Terraform resource definitions in configuration files
  • C. Credentials
  • D. State file

正解:B

解説:
When running a terraform apply -refresh-only, Terraform does not reference the configuration files, but only the state file, credentials, and cloud provider. The purpose of this command is to update the state file with the current status of the real resources, without making any changes to them1.


質問 # 86
Which configuration consistency errors does terraform validate report?

  • A. Terraform module isn't the latest version
  • B. Differences between local and remote state
  • C. Declaring a resource identifier more than once
  • D. A mix of spaces and tabs in configuration files

正解:C

解説:
Terraform validate reports configuration consistency errors, such as declaring a resource identifier more than once. This means that the same resource type and name combination isused for multiple resource blocks, which is not allowed in Terraform. For example, resource "aws_instance" "example" {...} cannot be used more than once in the same configuration. Terraform validate does not report errors related to module versions, state differences, or formatting issues, as these are not relevant for checking the configuration syntax and structure. References = [Validate Configuration], [Resource Syntax]


質問 # 87
Which of the following is not true of Terraform providers?

  • A. A community of users can maintain a provider
  • B. None of the above
  • C. An individual person can write a Terraform Provider
  • D. providers
  • E. Cloud providers and infrastructure vendors can write, maintain, or collaborate on Terraform
  • F. HashiCorp maintains some providers

正解:B

解説:
All of the statements are true of Terraform providers. Terraform providers are plugins that enable Terraform to interact with various APIs and services1. Anyone can write a Terraform provider, either as an individual or as part of a community2. HashiCorp maintains some providers, such as the AWS, Azure, and Google Cloud providers3. Cloud providers and infrastructure vendors can also write, maintain, or collaborate on Terraform providers, such as the VMware, Oracle, and Alibaba Cloud providers. Reference =
* 1: Providers - Configuration Language | Terraform | HashiCorp Developer
* 2: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer
* 3: Terraform Registry
* : Terraform Registry


質問 # 88
HashiCorp Configuration Language (HCL) supports user-denned functions.

  • A. False
  • B. True

正解:A

解説:
Explanation
HashiCorp Configuration Language (HCL) does not support user-defined functions. You can only use the built-in functions that are provided by the language. The built-in functions allow you to perform various operations and transformations on values within expressions. The general syntax for function calls is a function name followed by comma-separated arguments in parentheses, such as max(5, 12, 9). You can find the documentation for all of the available built-in functions in the Terraform Registry or the Packer Documentation, depending on which tool you are using. References = : Functions - Configuration Language | Terraform : Functions - Configuration Language | Packer


質問 # 89
Which of these is true about Terraform's plugin-based architecture?

  • A. You can create a provider for your API if none exists
  • B. Every provider in a configuration has its own state file for its resources
  • C. All providers are part of the Terraform core binary
  • D. Terraform can only source providers from the internet

正解:A

解説:
Terraform is built on a plugin-based architecture, enabling developers to extend Terraform by writing new plugins or compiling modified versions of existing plugins1. Terraform plugins are executable binaries written in Go that expose an implementation for a specific service, such as a cloud resource, SaaS platform, or API2. If there is no existing provider for your API, you can create one using the Terraform Plugin SDK3 or the Terraform Plugin Framework4. Reference =
* 1: Plugin Development - How Terraform Works With Plugins | Terraform | HashiCorp Developer
* 2: Lab: Terraform Plug-in Based Architecture - GitHub
* 3: Terraform Plugin SDK - Terraform by HashiCorp
* 4: HashiCorp Terraform Plugin Framework Now Generally Available


質問 # 90
Only the user that generated a plan may apply it.

  • A. False
  • B. True

正解:A

解説:
Explanation
Any user with permission to apply a plan can apply it, not only the user that generated it. This allows for collaboration and delegation of tasks among team members.


質問 # 91
......

合格率取得する秘訣はTerraform-Associate-003認定試験エンジンPDF:https://www.goshiken.com/HashiCorp/Terraform-Associate-003-mondaishu.html

Terraform-Associate-003試験問題集で合格できるには更新されたテスト問題集:https://drive.google.com/open?id=1v_QmDbNE2FgdeUl1OVsnlyRYnwYsa2-_