New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon DVA-C02 Exam - Topic 6 Question 15 Discussion

Actual exam question for Amazon's DVA-C02 exam
Question #: 15
Topic #: 6
[All DVA-C02 Questions]

An developer is building a serverless application by using the AWS Serverless Application Model (AWS SAM). The developer is currently testing the application in a development environment. When the application is nearly finsihed, the developer will need to set up additional testing and staging environments for a quality assurance team.

The developer wants to use a feature of the AWS SAM to set up deployments to multiple environments.

Which solution will meet these requirements with the LEAST development effort?

Show Suggested Answer Hide Answer
Suggested Answer: A

The correct answer is A. Add a configuration file in TOML format to group configuration entries to every environment. Add a table for each testing and staging environment. Deploy updates to the environments by using the sam deploy command and the --config-env flag that corresponds to the each environment.

A) Add a configuration file in TOML format to group configuration entries to every environment. Add a table for each testing and staging environment. Deploy updates to the environments by using the sam deploy command and the --config-env flag that corresponds to the each environment. This is correct. This solution will meet the requirements with the least development effort, because it uses a feature of the AWS SAM CLI that supports a project-level configuration file that can be used to configure AWS SAM CLI command parameter values1. The configuration file can have multiple environments, each with its own set of parameter values, such as stack name, region, capabilities, and more2. The developer can use the --config-env option to specify which environment to use when deploying the application3. This way, the developer can avoid creating multiple templates or scripts, or manually overriding parameters for each environment.

B) Create additional AWS SAM templates for each testing and staging environment. Write a custom shell script that uses the sam deploy command and the --template-file flag to deploy updates to the environments. This is incorrect. This solution will not meet the requirements with the least development effort, because it requires creating and maintaining multiple templates and scripts for each environment. This can introduce duplication, inconsistency, and complexity in the deployment process.

C) Create one AWS SAM configuration file that has default parameters. Perform updates to the testing and staging environments by using the ---parameter-overrides flag in the AWS SAM CLI and the parameters that the updates will override. This is incorrect. This solution will not meet the requirements with the least development effort, because it requires manually specifying and overriding parameters for each environment every time the developer deploys the application. This can be error-prone, tedious, and inefficient.

D) Use the existing AWS SAM template. Add additional parameters to configure specific attributes for the serverless function and database table resources that are in each environment. Deploy updates to the testing and staging environments by using the sam deploy command. This is incorrect. This solution will not meet the requirements with the least development effort, because it requires modifying the existing template and adding complexity to the resource definitions for each environment. This can also make it difficult to manage and track changes across different environments.


1: AWS SAM CLI configuration file - AWS Serverless Application Model

2: Configuration file basics - AWS Serverless Application Model

3: Specify a configuration file - AWS Serverless Application Model

Contribute your Thoughts:

0/2000 characters
Slyvia
3 months ago
Wait, are we really considering TOML for config? That’s unexpected!
upvoted 0 times
...
Jess
3 months ago
D could work, but adding too many parameters might complicate things.
upvoted 0 times
...
An
4 months ago
C is pretty straightforward, but not sure if it’s the least effort.
upvoted 0 times
...
Goldie
4 months ago
I disagree, B seems more organized with separate templates.
upvoted 0 times
...
Alishia
4 months ago
Option A sounds like the easiest way to manage multiple environments.
upvoted 0 times
...
Ivette
4 months ago
Option D seems straightforward since it suggests using the existing template and just adding parameters. I think that could work well, but I wonder if it might complicate things later on.
upvoted 0 times
...
Pa
4 months ago
I recall that using the --parameter-overrides flag in option C could streamline the process. It sounds familiar, but I’m not confident if it’s the least effort compared to the others.
upvoted 0 times
...
Tijuana
4 months ago
I think option B might require too much effort since it involves creating multiple templates and a custom script. We practiced a similar question, and it seemed like the simpler solutions were better.
upvoted 0 times
...
Jerry
5 months ago
I remember we discussed using configuration files in TOML format during our study sessions. It seems like option A could be a good fit, but I'm not entirely sure about the --config-env flag.
upvoted 0 times
...
Wai
5 months ago
I'm leaning towards option C with the parameter overrides. That way I don't have to create separate templates for each environment, which sounds like a lot of extra work. As long as I have the right parameter values set, I should be able to deploy updates pretty easily.
upvoted 0 times
...
Alease
5 months ago
Option A with the TOML config file seems like a pretty elegant solution. I like how it keeps all the environment-specific settings in one place. Plus, using the --config-env flag sounds like a nice, simple way to deploy to different environments. I think I'll go with that one.
upvoted 0 times
...
Ben
5 months ago
Hmm, I'm a bit confused by all the different options here. I'm not super familiar with AWS SAM yet, so I'll need to think this through carefully. Maybe I'll start by reviewing the AWS SAM documentation to understand the different deployment strategies better.
upvoted 0 times
...
Leonora
5 months ago
This looks like a pretty straightforward question about managing multiple environments with AWS SAM. I think I'll go with option D - using the existing template and adding parameters to configure the resources for each environment. That seems like the least amount of extra work.
upvoted 0 times
...
Roxane
5 months ago
Hmm, this one seems straightforward. I'd go with option A and update the fields directly on the Project page layout.
upvoted 0 times
...
Bethanie
5 months ago
Change planning seems like the most logical choice here. It's specifically focused on adapting to changing business needs.
upvoted 0 times
...
Clorinda
5 months ago
I'm not totally sure about this one, but B seems more like a P2P model with BitTorrent, right?
upvoted 0 times
...
Clorinda
5 months ago
I've done this a few times before, so I'm pretty confident. The two commands I'll choose are "compile" and "./configure". That should cover the full process of compiling and installing from source.
upvoted 0 times
...
Jimmie
5 months ago
It feels like I've seen a question similar to this before, maybe with different numbers. I think the dividend growth rate plays a big role, and using the share price in the denominator is crucial.
upvoted 0 times
...
Roselle
2 years ago
Haha, I'm just glad they're not asking us to manually create separate CloudFormation stacks for each environment. That would be a nightmare!
upvoted 0 times
...
Fletcher
2 years ago
Yeah, I was also considering option D. Having all the environment-specific configurations in the template itself seems cleaner and more maintainable in the long run. But I suppose option C is a bit simpler to set up initially.
upvoted 0 times
...
Elke
2 years ago
I agree, option C does sound the most efficient. Using parameter overrides to configure the different environments seems like the least development effort. Although, option D with the additional parameters in the template could work as well.
upvoted 0 times
...
Glenn
2 years ago
Hmm, this question seems to be testing our understanding of AWS SAM and how to manage deployments to multiple environments. I'm leaning towards option C, as it seems the most straightforward approach.
upvoted 0 times
...

Save Cancel