試験Terraform-Associate-004 トピック4 問題221 スレッド
HashiCorp Terraform-Associate-004のリアル試験問題集
問題 #: 221
トピック #: 4
問題 #: 221
トピック #: 4
Which argument can you set on a module block to prevent Terraform from updating the module's configuration during an init or get operation?
おすすめの解答：A 解答を投票する
Rationale for Correct answer: Setting the module version (for registry modules) pins the module release Terraform will use. By pinning the version, Terraform will not "update" the module to newer releases during terraform init -upgrade or terraform get -update unless you change the version constraint. This is the standard way to control module updates and keep module code stable across runs.
Analysis of Incorrect Options (Distractors):
B (lifecycle): lifecycle is for resources, not module blocks.
C (count): count controls how many module instances are created; it doesn't control module source updates.
D (source): source tells Terraform where the module comes from; it doesn't prevent updates by itself (a VCS/ref pin would be done in the source string, but the module block argument that achieves this in the typical module workflow is version for registry modules).
Key Concept: Module version pinning to control module upgrades.
Reference:
Analysis of Incorrect Options (Distractors):
B (lifecycle): lifecycle is for resources, not module blocks.
C (count): count controls how many module instances are created; it doesn't control module source updates.
D (source): source tells Terraform where the module comes from; it doesn't prevent updates by itself (a VCS/ref pin would be done in the source string, but the module block argument that achieves this in the typical module workflow is version for registry modules).
Key Concept: Module version pinning to control module upgrades.
Reference:
Asaoka 2026-07-24 11:01:27
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン （無料です）。