Terraform Associate Exam QuestionsBrowse all questions from this exam

Terraform Associate Exam - Question 36


What value does the Terraform Cloud/Terraform Enterprise private module registry provide over the public Terraform Module Registry?

Show Answer
Correct Answer: C

The Terraform Cloud/Terraform Enterprise private module registry provides the ability to restrict modules to members of Terraform Cloud or Enterprise organizations. This feature ensures that sensitive infrastructure code and proprietary modules are kept private within an organization, providing an additional level of control and security in comparison to the public Terraform Module Registry, which is accessible to everyone.

Discussion

22 comments
Sign in to comment
vitasacOption: C
Apr 29, 2022

for sure C

tipzzzOption: C
Apr 24, 2022

Terraform Cloud's private registry works similarly to the public Terraform Registry and helps you share Terraform providers and Terraform modules across your organization. It includes support for versioning and a searchable list of available providers and modules.

campsOption: C
Apr 1, 2023

C. The ability to restrict modules to members of Terraform Cloud or Enterprise organizations. The private module registry in Terraform Cloud/Terraform Enterprise provides an additional level of control and security over the public Terraform Module Registry. Unlike the public registry, the private registry allows organizations to restrict module access to only members of their Terraform Cloud or Enterprise organization. This ensures that sensitive infrastructure code is not accidentally or intentionally shared with unauthorized users.

BereOption: C
Jul 29, 2023

The private module registry in Terraform Cloud and Terraform Enterprise is a way to distribute Terraform modules within your organization. The public Terraform Module Registry, on the other hand, is open to everyone. Here is an example of how you might use a module from a private module registry: module "vpc" { source = "app.terraform.io/example_corp/vpc/aws" version = "1.0.0" // ...other arguments... } Here is an example of how you might use a module from the public Terraform Module Registry: module "vpc" { source = "terraform-aws-modules/vpc/aws" version = "2.77.0" // ...other arguments... }

Yhorm
Nov 2, 2023

sometime I wonder whether whomever picked the 'correct' answers just picked an alternative at random

legendary7
Sep 27, 2022

C - is the correct answer. D- is simply the advantage of Public registry over Private registry. It is the opposite of what the question asks

BereOption: C
Dec 20, 2022

https://developer.hashicorp.com/terraform/cloud-docs/registry Private Registry Terraform Cloud's private registry works similarly to the public Terraform Registry and helps you share Terraform providers and Terraform modules across your organization. It includes support for versioning and a searchable list of available providers and modules. https://developer.hashicorp.com/terraform/cloud-docs/registry#private-providers-and-modules Private Providers and Modules Private providers and private modules are hosted on an organization's private registry and are only available to members of that organization. In Terraform Enterprise, private modules are also available to other organizations that are configured to share modules with that organization.

campsOption: C
Mar 31, 2023

C. The ability to restrict modules to members of Terraform Cloud or Enterprise organizations. The Terraform Module Registry is a public repository of Terraform modules that can be used by anyone using Terraform. The Terraform Cloud/Terraform Enterprise private module registry provides additional functionality for organizations that want to create and manage their own private modules. The private module registry provides several benefits over the public Terraform Module Registry, including: The ability to restrict modules to members of Terraform Cloud or Enterprise organizations: This allows organizations to control who has access to their private modules and prevent unauthorized access. The ability to tag modules by version or release: This makes it easy to manage and track changes to modules over time. The ability to manage module dependencies: This allows organizations to manage and version the dependencies of their private modules. Integration with Terraform Cloud or Enterprise workspaces: This allows organizations to seamlessly use their private modules in their Terraform Cloud or Enterprise workspaces.

temp111
May 6, 2022

Answer is C

fabiomlopOption: C
Jun 18, 2022

It's a private registry, therefore you can make it private LOL

Shane_COption: C
Jul 4, 2023

Come on guys, it's C

samimshaikhOption: C
Dec 29, 2023

the question has the word private registry "over" the public C. The ability to restrict modules to members of Terraform Cloud or Enterprise organizations The Terraform Cloud/Terraform Enterprise private module registry provides the ability to restrict modules to members of specific Terraform Cloud or Enterprise organizations. This allows organizations to control access to and usage of modules, keeping them private within the organization. Option C correctly describes this capability.

ParthasarathiOption: C
May 13, 2022

It should be C

EltoothOption: C
Jun 26, 2022

C is correct answer.

yuvifoseOption: C
Jul 18, 2022

The answer should be C

mendelthegreat
Oct 30, 2022

C is the correct answer DUH

alexsandroeOption: C
Feb 25, 2023

C is correct

Power123
Mar 30, 2023

Answer is C

FaaizzOption: C
Apr 4, 2023

Only C makes sense here

Ni33Option: C
May 8, 2023

C is the correct answer

hoangphanOption: C
Jan 30, 2024

of course C

anand0310Option: C
Aug 31, 2024

Private registry is meant for restricting access to just the organization's teams