Amazon Web Services Updated SOA-C02 Exam Questions and Answers by niam

Amazon Route 53's failover routing policy allows you to route traffic to a primary resource unless it is unavailable, in which case Route 53 can fail over to a secondary resource.

Steps:

Open Route 53 Console:

Open the Amazon Route 53 console.

Create Alias Records:

In your hosted zone, create two alias records.

One alias record should point to the ALB in the primary region and the other to the ALB in the secondary region.

Set Failover Routing Policy:

For the alias record pointing to the primary ALB, set the routing policy to "Failover" and designate it as the primary.

For the alias record pointing to the secondary ALB, set the routing policy to "Failover" and designate it as the secondary.

Enable Health Checks:

Ensure that "Evaluate Target Health" is set to "Yes" for both alias records. This ensures that Route 53 will check the health of the ALBs before routing traffic.

Configure Health Checks for ALBs:

Ensure that each ALB has appropriate health checks configured to accurately report the health of the instances.

References:

Route 53 Failover Routing

Configuring Alias Records

Dedicated Hosts are physical servers that are dedicated to a single customer, ensuring that the customer’s workloads are not shared with other customers or with other AWS accounts within the company. This will ensure that the company’s security policy is followed and that sensitive workloads are running on hardware that is not shared with other customers or with other AWS accounts within the company.

To ensure that the AWS CloudFormation template works in every region, you should use the Mappings section to specify region-specific AMI IDs. This allows the template to dynamically reference the correct AMI ID based on the region where the stack is being deployed.

Steps:

Add Mappings to the Template:

Define the AMI IDs for each region in the Mappings section of the CloudFormation template.

json

Copy code

{

"Mappings": {

"RegionMap": {

"us-east-1": { "AMI": "ami-0123456789abcdef0" },

"us-west-2": { "AMI": "ami-abcdef0123456789" }

}

}

}

Reference the Mapping in the Template:

Use the Fn::FindInMap function to reference the correct AMI ID based on the region.

json

Copy code

{

"Resources": {

"MyEC2Instance": {

"Type": "AWS::EC2::Instance",

"Properties": {

"ImageId": { "Fn::FindInMap": [ "RegionMap", { "Ref": "AWS::Region" }, "AMI" ] },

}

}

}

}

Deploy the Template:

Deploy the CloudFormation stack in any region, and it will use the correct AMI ID.

Enable Amazon S3 Transfer Acceleration Amazon S3 Transfer Acceleration can provide fast and secure transfers over long distances between your client and Amazon S3. Transfer Acceleration uses Amazon CloudFront's globally distributed edge locations. https://aws.amazon.com/premiumsupport/knowledge-center/s3-upload-large-files/