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 SAA-C03 Exam - Topic 1 Question 39 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 39
Topic #: 1
[All SAA-C03 Questions]

A company is deploying an application in three AWS Regions using an Application Load Balancer Amazon Route 53 will be used to distribute traffic between these Regions. Which Route 53 configuration should a solutions architect use to provide the MOST high-performing experience?

Show Suggested Answer Hide Answer
Suggested Answer: B

This solution meets the requirements most cost-effectively because it enables the company to migrate its on-premises NFS data store to AWS without changing the existing applications or workflows. AWS Storage Gateway is a hybrid cloud storage service that provides seamless and secure integration between on-premises and AWS storage. Amazon S3 File Gateway is a type of AWS Storage Gateway that provides a file interface to Amazon S3, with local caching for low-latency access. By setting up an Amazon S3 File Gateway, the company can store and retrieve files as objects in Amazon S3 using standard file protocols such as NFS. The company can also use an Amazon S3 Lifecycle policy to automatically transition the data to the appropriate storage class based on the frequency of access and the cost of storage. For example, the company can use S3 Standard for frequently accessed data, S3 Standard-Infrequent Access (S3 Standard-IA) or S3 One Zone-Infrequent Access (S3 One Zone-IA) for less frequently accessed data, and S3 Glacier or S3 Glacier Deep Archive for long-term archival data.

Option A is not a valid solution because AWS Storage Gateway Volume Gateway is a type of AWS Storage Gateway that provides a block interface to Amazon S3, with local caching for low-latency access. Volume Gateway is not suitable for migrating an NFS data store, as it requires attaching the volumes to EC2 instances or on-premises servers using the iSCSI protocol. Option C is not a valid solution because Amazon Elastic File System (Amazon EFS) is a fully managed elastic NFS file system that is designed for workloads that require high availability, scalability, and performance. Amazon EFS Standard-Infrequent Access (Standard-IA) is a storage class within Amazon EFS that is optimized for infrequently accessed files, with a lower price per GB and a higher price per access. Using Amazon EFS Standard-IA for migrating an NFS data store would not be cost-effective, as it would incur higher access charges and require additional configuration to enable lifecycle management. Option D is not a valid solution because Amazon EFS One Zone-Infrequent Access (One Zone-IA) is a storage class within Amazon EFS that is optimized for infrequently accessed files that do not require the availability and durability of Amazon EFS Standard or Standard-IA. Amazon EFS One Zone-IA stores data in a single Availability Zone, which reduces the cost by 47% compared to Amazon EFS Standard-IA, but also increases the risk of data loss in the event of an Availability Zone failure. Using Amazon EFS One Zone-IA for migrating an NFS data store would not be cost-effective, as it would incur higher access charges and require additional configuration to enable lifecycle management. It would also compromise the availability and durability of the data.


AWS Storage Gateway - Amazon Web Services

Amazon S3 File Gateway - AWS Storage Gateway

Object Lifecycle Management - Amazon Simple Storage Service

[AWS Storage Gateway Volume Gateway - AWS Storage Gateway]

[Amazon Elastic File System - Amazon Web Services]

[Using EFS storage classes - Amazon Elastic File System]

Contribute your Thoughts:

0/2000 characters
Shannon
3 months ago
I’m surprised latency isn’t the default choice for this scenario!
upvoted 0 times
...
Maynard
3 months ago
Geoproximity sounds interesting, but does it really outperform latency?
upvoted 0 times
...
Susana
3 months ago
CNAME with failover? Not sure that’s the best choice here.
upvoted 0 times
...
Darell
4 months ago
I think geolocation might be better for user experience.
upvoted 0 times
...
Elvera
4 months ago
A latency policy is usually the best for performance!
upvoted 0 times
...
Genevive
4 months ago
I have a vague memory of geoproximity policies, but I'm not confident they would outperform latency policies in this scenario.
upvoted 0 times
...
Cassi
4 months ago
I practiced a similar question about load balancing and I feel like latency policies were emphasized as the best choice for performance.
upvoted 0 times
...
Juan
4 months ago
I'm not entirely sure, but I think geolocation policies might be better for targeting specific user demographics rather than performance.
upvoted 0 times
...
Shawnda
5 months ago
I remember studying latency policies in Route 53, and I think they help direct users to the closest region based on response times.
upvoted 0 times
...
Karrie
5 months ago
I'm not sure if the failover policy is the right choice here. That's more for disaster recovery, not necessarily optimizing performance across Regions.
upvoted 0 times
...
Curt
5 months ago
Okay, I've got this. The question is asking for the most high-performing experience, so I'm going to go with the latency policy. That should route traffic to the closest Region for the best performance.
upvoted 0 times
...
Jenise
5 months ago
Hmm, I'm a bit confused on the differences between the latency, geolocation, and geoproximity policies. I'll need to review those before deciding.
upvoted 0 times
...
Chaya
5 months ago
This looks like a tricky one, but I think I can figure it out. The key is understanding the different Route 53 policies and how they impact performance.
upvoted 0 times
...
Tish
5 months ago
Ooh, this is a good one. The consultant will probably tell them to weigh the benefits of BYOD against the privacy risks. They'll need a comprehensive policy that protects the business while respecting employees' rights.
upvoted 0 times
...
Jamal
5 months ago
Okay, let's see. Partial encryption of a request, authentication of a request, and SAML token propagation - those sound like the key security schemes supported by OSB. I'll go with those three.
upvoted 0 times
...
Jolanda
5 months ago
This looks like a straightforward question on the activities involved in the Continuous Monitoring phase of the security certification and accreditation process. I'll review the options carefully and select the ones that represent complete solutions.
upvoted 0 times
...
Lynelle
10 months ago
I don't know, maybe we should just flip a coin and call it a day. That's probably more accurate than these fancy routing policies, am I right?
upvoted 0 times
...
Kenneth
10 months ago
You're all overthinking this. Option C is clearly the way to go - failover policy is the best for high availability, and CNAME records are more flexible than A records. Easy peasy!
upvoted 0 times
Galen
8 months ago
Option C is definitely the way to go for high availability and flexibility. Let's stick with that choice.
upvoted 0 times
...
Ciara
8 months ago
But what about Option A with weighted routing policy? Wouldn't that also help distribute traffic effectively?
upvoted 0 times
...
Felix
8 months ago
I agree, Option C with failover policy and CNAME records is the best choice for high performance.
upvoted 0 times
...
...
Thora
10 months ago
Hold up, why not a CNAME record with a geoproximity policy? That way we can fine-tune the traffic distribution based on the user's location and proximity to the regions.
upvoted 0 times
...
Quentin
10 months ago
Hmm, I was leaning towards option B. Geolocation-based routing could be useful if we need to target specific geographic areas.
upvoted 0 times
Tresa
10 months ago
I agree, it could be very useful for distributing traffic efficiently across different regions.
upvoted 0 times
...
Luis
10 months ago
Option B sounds like a good choice. Geolocation-based routing can definitely help target specific geographic areas.
upvoted 0 times
...
...
Soledad
10 months ago
Hmm, that's an interesting point. Can you explain why you think that option is better?
upvoted 0 times
...
Hoa
10 months ago
I disagree, I believe creating a CNAME record with a geoproximity policy would provide the most high-performing experience.
upvoted 0 times
...
Soledad
10 months ago
I think the best option is to create an A record with a latency policy.
upvoted 0 times
...
Meghann
11 months ago
I think option A is the way to go. Latency-based routing is perfect for delivering the best performance across multiple regions.
upvoted 0 times
Luis
9 months ago
I've had success with using latency-based routing in the past. It really does help optimize performance across different AWS Regions.
upvoted 0 times
...
Victor
9 months ago
It's important to prioritize performance when deploying applications in multiple regions. Option A with latency-based routing is the most high-performing configuration.
upvoted 0 times
...
Franklyn
10 months ago
I agree, using latency-based routing with Route 53 is the way to go for distributing traffic across multiple AWS Regions.
upvoted 0 times
...
Lorriane
10 months ago
Option A is definitely the best choice. Latency-based routing will ensure the highest performance.
upvoted 0 times
...
...
Tiera
11 months ago
I'm not sure, but I think creating a CNAME record with a failover policy could also be a good option.
upvoted 0 times
...
Danilo
11 months ago
I disagree, I believe creating a CNAME record with a geoproximity policy would provide the most high-performing experience.
upvoted 0 times
...
Ira
11 months ago
I think the best option is to create an A record with a latency policy.
upvoted 0 times
...

Save Cancel