Provider dependencies are created in several different ways. Select the valid provider dependencies from the following list: (select three)

Question

Options

• AExplicit use of a provider block in configuration, optionally including a version constraint.
• BUse of any resource belonging to a particular provider in a resource or data block in
• CExistence of any resource instance belonging to a particular provider in the current state.
• DExistence of any provider plugins found locally in the working directory.

• A
  89% (24)
• D
  11% (3)

Explanation

Terraform creates provider dependencies in three ways: (A) An explicit provider block in configuration, optionally specifying a version constraint - this directly declares the dependency. (B) Any resource or data block that references a provider's resource type implicitly creates a dependency on that provider. (C) If existing resource instances for a provider exist in the current state file, Terraform maintains a dependency on that provider to manage those resources. Choice D is incorrect - the mere presence of provider plugin binaries in the local working directory does not create a dependency. Dependencies are driven by configuration and state, not local file system contents.

No community discussion yet for this question.