Terraform can import modules from a number of sources; which of the following is not a valid source?

Terraform can import modules from a number of sources; which of the following is not a valid source?

• A. GitHub repository
• B. Local path
• C. Terraform Module Registry
• D. FTP server

Answer: (D)

Terraform can bring in modules from sources it can fetch through its standard fetchers: a path on your local filesystem, a version-control repository (like GitHub, GitLab, or Bitbucket via a git URL), or the Terraform Module Registry by name. An FTP server isn’t supported as a module source because Terraform’s module fetcher does not know how to retrieve or unpack modules from FTP URLs; it expects local paths, VCS URLs, or registry references. That’s why an FTP server cannot be used to import modules in Terraform. The other options—GitHub repository, local path, and the Terraform Module Registry—are valid sources because they align with Terraform’s supported ways to locate and download modules.

Terraform can bring in modules from sources it can fetch through its standard fetchers: a path on your local filesystem, a version-control repository (like GitHub, GitLab, or Bitbucket via a git URL), or the Terraform Module Registry by name. An FTP server isn’t supported as a module source because Terraform’s module fetcher does not know how to retrieve or unpack modules from FTP URLs; it expects local paths, VCS URLs, or registry references. That’s why an FTP server cannot be used to import modules in Terraform. The other options—GitHub repository, local path, and the Terraform Module Registry—are valid sources because they align with Terraform’s supported ways to locate and download modules.