Creating Template3 by Defining Bicep Modules That Reuse Logic from Template1 and Template2

Why the Answer Is Correct

The requirement is that Template3 reuses logic from Template1 and Template2, and Bicep provides a specific construct for composing templates: modules. A module references another Bicep or ARM template as a callable building block, exposing its parameters and outputs so the calling template can wire them together. Because a module reference must exist before it can be used, the modules definition is the first thing to declare in Template3. The vote was unanimous at 100 for C. p2006 supplied the authoritative Microsoft Learn page on Bicep modules, and Mattt drew the right analogy by noting that this is the same modular reuse pattern as Terraform modules, which confirms the concept is about composition rather than about any single template section.

Why the Other Options Are Wrong

Parameters (D) are inputs passed into a template, and declaring them says nothing about pulling in other templates, so a Template3 with only parameters would still have to duplicate the VM and website logic. Outputs (A) are the values a template exports to its caller, which is a data flow out of the template rather than a mechanism for composing templates, and in Bicep outputs cannot be declared at the top level in a way that constitutes reuse. The resources block (B) declares the actual infrastructure items a template deploys, so using it in Template3 would mean writing the virtual machine and website again inline, which is duplication rather than the reuse the question asks for.

Community Comment Notes

The community was unanimous at 100 for C, and both substance comments identify modules as the reuse construct. p2006 linked the official Bicep modules documentation, which is the verifiable basis for the answer. Mattt's comment adds the useful framing that modules are to Bicep what modules are to Terraform, which is exactly the right mental model for understanding why modules must be defined before use. The absence of dissent reflects that the other three options are familiar template sections that simply do not perform cross-template composition.