exam questions

Exam AWS Certified Solutions Architect - Professional All Questions

View all questions & answers for the AWS Certified Solutions Architect - Professional exam

Exam AWS Certified Solutions Architect - Professional topic 1 question 490 discussion

A Development team has created a series of AWS CloudFormation templates to help deploy services. They created a template for a network/virtual private cloud
(VPC) stack, a database stack, a bastion host stack, and a web application-specific stack. Each service requires the deployment of at least:
✑ A network/VPC stack
✑ A bastion host stack
✑ A web application stack
Each template has multiple input parameters that make it difficult to deploy the services individually from the AWS CloudFormation console. The input parameters from one stack are typically outputs from other stacks. For example, the VPC ID, subnet IDs, and security groups from the network stack may need to be used in the application stack or database stack.
Which actions will help reduce both the operational burden and the number of parameters passed into a service deployment? (Choose two.)

  • A. Create a new AWS CloudFormation template for each service. Alter the existing templates to use cross-stack references to eliminate passing many parameters to each template. Call each required stack for the application as a nested stack from the new stack. Call the newly created service stack from the AWS CloudFormation console to deploy the specific service with a subset of the parameters previously required.
  • B. Create a new portfolio in AWS Service Catalog for each service. Create a product for each existing AWS CloudFormation template required to build the service. Add the products to the portfolio that represents that service in AWS Service Catalog. To deploy the service, select the specific service portfolio and launch the portfolio with the necessary parameters to deploy all templates.
  • C. Set up an AWS CodePipeline workflow for each service. For each existing template, choose AWS CloudFormation as a deployment action. Add the AWS CloudFormation template to the deployment action. Ensure that the deployment actions are processed to make sure that dependencies are obeyed. Use configuration files and scripts to share parameters between the stacks. To launch the service, execute the specific template by choosing the name of the service and releasing a change.
  • D. Use AWS Step Functions to define a new service. Create a new AWS CloudFormation template for each service. Alter the existing templates to use cross- stack references to eliminate passing many parameters to each template. Call each required stack for the application as a nested stack from the new service template. Configure AWS Step Functions to call the service template directly. In the AWS Step Functions console, execute the step.
  • E. Create a new portfolio for the services in AWS Service Catalog. Create a new AWS CloudFormation template for each service. Alter the existing templates to use cross-stack references to eliminate passing many parameters to each template. Call each required stack for the application as a nested stack from the new stack. Create a product for each application. Add the service template to the product. Add each new product to the portfolio. Deploy the product from the portfolio to deploy the service with the necessary parameters only to start the deployment.
Show Suggested Answer Hide Answer
Suggested Answer: AE 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Bulti
Highly Voted 3 years, 7 months ago
A&E. E requires few parameters and one action to launch a portfolio to deploy all products, where one product represents one service. Between A ( CloudFormation console to deploy a service) vs D ( Step function to deploy a service) I chose A because I didn't find Step function to be a standard practice to deploy a cloudformation stack unlike CodePipeline which is a standard way to test and deploy cloudformation stack via a codepipeline. However Option B and C fall short because they do not reduce the# of input parameters.
upvoted 10 times
...
NNHAN
Highly Voted 3 years, 8 months ago
A and E
upvoted 6 times
keos
3 years, 8 months ago
they have duplicate content
upvoted 1 times
...
Kelvin1477
3 years, 7 months ago
Agree, Looks like the only option to pass parameter around is still using nested cloudformation templates
upvoted 1 times
...
...
SkyZeroZx
Most Recent 1 year, 11 months ago
Selected Answer: AE
Option B suggests creating a new portfolio in AWS Service Catalog for each service and creating a product for each existing AWS CloudFormation template required to build the service. While AWS Service Catalog can help with managing and provisioning services, it may not directly address the issue of reducing the number of parameters passed into a service deployment. Options A and E, on the other hand, specifically suggest using cross-stack references within AWS CloudFormation templates to eliminate the need for passing many parameters. This approach directly tackles the issue of parameter management and reduces the operational burden by making the templates more modular and self-contained.
upvoted 1 times
SkyZeroZx
1 year, 11 months ago
Therefore, options A and E are more suitable for reducing the operational burden and minimizing the number of parameters passed into a service deployment, as stated in the question.
upvoted 1 times
...
...
ASC1
2 years, 12 months ago
why not B ?
upvoted 1 times
...
tkanmani76
3 years, 4 months ago
A and E - Pl refer this article - https://aws.amazon.com/blogs/mt/how-to-launch-secure-and-governed-aws-resources-with-aws-cloudformation-and-aws-service-catalog/
upvoted 1 times
...
AzureDP900
3 years, 5 months ago
AE is correct, There is no need of codepipeline.
upvoted 1 times
...
WhyIronMan
3 years, 6 months ago
I will go with A, E
upvoted 4 times
...
MarcChartouny
3 years, 6 months ago
I got lost since I don't have the advanced DevOps expertise, But my guts tell me to go with D & E. Please any DevOps engineers to assist and give their feedback?
upvoted 1 times
...
Waiweng
3 years, 6 months ago
It's A , E
upvoted 4 times
...
SD13
3 years, 6 months ago
D & E are the correct options that eliminate param passing. All other options still require params and no easy way to implement.
upvoted 2 times
...
Kian1
3 years, 6 months ago
going with AE
upvoted 2 times
...
Ebi
3 years, 6 months ago
I will go with AE
upvoted 4 times
...
Britts
3 years, 7 months ago
why not D & E, step functions can launch a stack? i.e. one step function per service
upvoted 1 times
...
arulrajjayaraj
3 years, 7 months ago
A & E - A --> AWS CloudFormation console to deploy , E -->ServiceCatalog , Cross Stacks When you need to pass export values to many stacks (VPC Id, etc…) & Nested Stacks • Helpful when components must be re-used • Ex: re-use how to properly configure an Application Load Balancer • The nested stack only is important to the higher level stack (it’s not shared)
upvoted 1 times
...
T14102020
3 years, 7 months ago
Correct AE. ServiceCatalog + without CodePipeline + without Step Functions
upvoted 1 times
Aquavk
3 years, 7 months ago
Why not D & E ?
upvoted 2 times
...
...
joos
3 years, 7 months ago
A and E
upvoted 2 times
...
alexmena1981
3 years, 7 months ago
E ok, why not D?
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...