Which solution will meet this requirement?

Explanations:

CloudFormation change sets are used to preview the changes that will be made to a stack before executing those changes. They do not facilitate the reuse of components across multiple templates or create dedicated templates for common components.

CloudFormation macros are a way to extend the CloudFormation language by enabling the transformation of templates at runtime. While they allow for some customization and reuse, they do not specifically address the need for creating dedicated templates for common components with their own parameters and conditions.

CloudFormation nested stacks allow you to create a parent stack that contains multiple child stacks. This enables the reuse of common components across multiple templates, as each child stack can have its own parameters and conditions, making it a suitable solution for the scenario described.

CloudFormation stack sets are used to manage stacks across multiple AWS accounts and regions, allowing you to deploy the same stack configuration to multiple accounts/regions simultaneously. This does not meet the requirement of creating dedicated templates for common components within a single account or region.