nerdexam
Amazon

DVA-C02 · Question #130

A developer needs to build an AWS CloudFormation template that self-populates the AWS Region variable that deploys the CloudFormation template. What is the MOST operationally efficient way to…

The correct answer is A. Use the AWS::Region pseudo parameter. CloudFormation pseudo parameters like AWS::Region are built-in, automatically resolved values that eliminate the need for manual input or complex parsing.

Submitted by klara.se· Mar 5, 2026Development with AWS Services

Question

A developer needs to build an AWS CloudFormation template that self-populates the AWS Region variable that deploys the CloudFormation template. What is the MOST operationally efficient way to determine the Region in which the template is being deployed?

Options

  • AUse the AWS::Region pseudo parameter.
  • BRequire the Region as a CloudFormation parameter.
  • CFind the Region from the AWS::StackId pseudo parameter by using the Fn::Split intrinsic function.
  • DDynamically import the Region by referencing the relevant parameter in AWS Systems Manager

How the community answered

(61 responses)
  • A
    90% (55)
  • B
    2% (1)
  • C
    3% (2)
  • D
    5% (3)

Why each option

CloudFormation pseudo parameters like AWS::Region are built-in, automatically resolved values that eliminate the need for manual input or complex parsing.

AUse the AWS::Region pseudo parameter.Correct

AWS::Region is a CloudFormation pseudo parameter that automatically resolves to the AWS Region where the stack is being deployed, requiring no manual input, parsing, or external lookups, making it the simplest and most operationally efficient approach.

BRequire the Region as a CloudFormation parameter.

Requiring the Region as a CloudFormation parameter forces deployers to manually input the value, introducing human error and unnecessary operational overhead when a built-in pseudo parameter already provides this automatically.

CFind the Region from the AWS::StackId pseudo parameter by using the Fn::Split intrinsic function.

Parsing the Region from AWS::StackId using Fn::Split is technically possible but unnecessarily complex and fragile compared to using the dedicated AWS::Region pseudo parameter.

DDynamically import the Region by referencing the relevant parameter in AWS Systems Manager

Importing the Region from AWS Systems Manager Parameter Store adds an external dependency and additional configuration steps when the information is already natively available as a pseudo parameter.

Concept tested: CloudFormation AWS::Region pseudo parameter usage

Source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/pseudo-parameter-reference.html

Community Discussion

No community discussion yet for this question.

Full DVA-C02 Practice