Exam AWS Certified DevOps Engineer - Professional DOP-C02 topic 1 question 39 discussion

100% D. AWS Service Catalog lets you centrally manage your cloud resources to achieve governance at scale of your infrastructure as code (IaC) templates, written in CloudFormation or Terraform configurations. With AWS Service Catalog, you can meet your compliance requirements while making sure your customers can quickly deploy the cloud resources they need. https://aws.amazon.com/servicecatalog/ all other service in other answer is not related.

Service Catalogue is a like a internal marketplace for an organization in that accounts in that organization are limited to using only the resources describe in the product catalogue. For the use case described the best choice is using Service Catalogue.

keywords: strict tagging, resource requirements a, limit the deployment AWS Service Catalog

D would be a better option, especially for developers, to abstract configuring the CloudFormation StackSets when launching applications with diverse versions. In AWS Service Catalog, they would just pick up the version and deploy. Everything would be set for them in the background including the CloudFormation StackSet with the version parameter and the tagging enforcement.

I'd argue that the correct answer is to use Service Catalog and StackSets. Option "D:" doesn't preclude using StackSets, it just doesn't mention it as part of the solution. ServiceCatalog is the formal method to distribute standard solutions (such as CloudFormation StackSets)

"A provisioned Service Catalog product is an AWS CloudFormation stack" Really confusing. I go with D...

AWS Service Catalog can be used to deploy resources to two regions (or even more) with the help of AWS CloudFormation StackSets. So Answer is C

Answer C If rules are applied across multiple accounts, the StackSets feature is more suitable. The service catalog is used for provisioning new accounts under the AWS control tower.

It's D

Service Catalog cannot ensures that the same application can be deployed to multiple regions.

D is correct: Catalog product impose strict requirements for app deloyment. If using stacksets, devs can deploy app to everywhere without any restrictions

To restrict regions or accounts where catalog products can be deployed, refer to AWS Service Catalog Stack Set Constraints (https://docs.aws.amazon.com/servicecatalog/latest/adminguide/constraints-stackset.html),

I will go with D. Reference here: https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/manage-aws-service-catalog-products-in-multiple-aws-accounts-and-aws-regions.html

While stacksets and catalog can use in this case catalog can restrict the strick policy than stacksets. The company has strict tagging and resource requirements.. So it's product catalog. in stacksets developers can modify the resources since they can get hold the template.

Answer is D. "Developers will need to deploy" multiple versions of the same application. So service catalog products will be best for developers.

The correct answer is: C. Create CloudFormation StackSets with approved CloudFormation templates. CloudFormation StackSets enable you to deploy stacks across multiple accounts and Regions using a single template. This allows you to enforce company policy by only allowing developers to use approved templates. AWS Service Catalog products can be used to launch approved CloudFormation templates, but they do not enforce the use of approved templates.

The best solution to ensure that resources are deployed in accordance with company policy is to create CloudFormation StackSets with approved CloudFormation templates. CloudFormation StackSets allow you to create and manage stacks across multiple AWS accounts and Regions. You can specify the template to use when creating a StackSet, as well as any parameters and capabilities that the template requires. By using approved CloudFormation templates, you can ensure that all resources deployed by the StackSet meet your company's tagging and resource requirements. You can also use StackSets to limit the deployment to two Regions. The other options are not as effective: