Exam AWS-SysOps topic 1 question 673 discussion

As per the question requirement : Single template that can be reused for multiple environments. Ans B is more suitable. Reasons ******* For A: If you want to use same teplate with multiple envt with Little changes especially Input or map or condition related then, A is good. For B : If you dont want to change anything in your template and if requires simply to run any envt without changes then, B is the right one.

B https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html#stackpolicy

Option A, using parameters, provides a flexible and customizable approach to infrastructure deployment, enabling the use of a single template for multiple environments while allowing environment-specific customization through parameter values.

Vote for A

To make templates reusable, use the parameters, mappings, and conditions sections so that you can customize your stacks when you create them. Response is A

A - It says it here "https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html#stackpolicy" - Reuse templates to replicate stacks in multiple environments: After you have your stacks and resources set up, you can reuse your templates to replicate your infrastructure in multiple environments. For example, you can create environments for development, testing, and production so that you can test changes before implementing them into production. To make templates reusable, use the parameters, mappings, and conditions sections so that you can customize your stacks when you create them. For example, for your development environments, you can specify a lower-cost instance type compared to your production environment, but all other configurations and settings remain the same. For more information about parameters, mappings, and conditions, see

A is the answer As a SINGLE template will be used for all environment, the parameters are the way to make the necessary changes, so the template can be used in other environments

A. Use parameters to provision the resources.

its should be A as -->Nested stacks are stacks created as part of other stacks hence D is wrong

Answer is A. See AWS documents on cloud formation best practice. In it, bit states to the use of parameters among other things for templates reusable.

A for me definitely

The answer is A: If you want to reuse your templet across other regions or other AWS accounts we use AWS parameters

I'll go with A

A. Use parameters to provision the resources.

A. Use parameters to provision the resources. Reuse templates to replicate stacks in multiple environments After you have your stacks and resources set up, you can reuse your templates to replicate your infrastructure in multiple environments. For example, you can create environments for development, testing, and production so that you can test changes before implementing them into production. To make templates reusable, use the parameters, mappings, and conditions sections so that you can customize your stacks when you create them. For example, for your development environments, you can specify a lower-cost instance type compared to your production environment, but all other configurations and settings remain the same. For more information about parameters, mappings, and conditions, see Template anatomy. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/best-practices.html#reuse

definitely A , If you want to reuse your templates across the company use param

Single Template, Reusable, Choice is A