QUESTION: 285

A solutions architect must update an application environment within AWS Elastic Beanstalk using a blue/green deployment methodology. The solutions architect creates an environment that is identical to the existing application environment and deploys the application to the new environment.

What should be done next to complete the update?

Redirect to the new environment using Amazon Route 53.
Select the Swap Environment URLs option.
Replace the Auto Scaling launch configuration.
Update the DNS records to point to the green environment.

Answer(s): B

Explanation:

B) In AWS Elastic Beanstalk, to complete a blue/green deployment, you use the Swap Environment URLs option. This option seamlessly switches the CNAME between the environments, redirecting traffic from the old (blue) environment to the new (green) environment without needing manual DNS updates.
A) and D) involve manually updating DNS or redirecting, which Elastic Beanstalk handles automatically with the Swap Environment URLs feature.
C) Replacing the Auto Scaling launch configuration is not part of the blue/green deployment process in Elastic Beanstalk.

Reveal Solution Next Question

QUESTION: 286

A company is building an image service on the web that will allow users to upload and search random photos. At peak usage, up to 10,000 users worldwide will upload their images. The will then overlay text on the uploaded images, which will then be published on the company website.

Which design should a solutions architect implement?

Store the uploaded images in Amazon Elastic File System (Amazon EFS). Send application log information about each image to Amazon CloudWatch Logs. Create a fleet of Amazon EC2 instances that use CloudWatch Logs to determine which images need to be processed. Place processed images in another directory in Amazon EFS. Enable Amazon CloudFront and configure the origin to be the one of the EC2 instances in the fleet.
Store the uploaded images in an Amazon S3 bucket and configure an S3 bucket event notification to send a message to Amazon Simple Notification Service (Amazon SNS). Create a fleet of Amazon EC2 instances behind an Application Load Balancer (ALB) to pull messages from Amazon SNS to process the images and place them in Amazon Elastic File System (Amazon EFS). Use Amazon CloudWatch metrics for the SNS message volume to scale out EC2 instances. Enable Amazon CloudFront and configure the origin to be the ALB in front of the EC2 instances.
Store the uploaded images in an Amazon S3 bucket and configure an S3 bucket event notification to send a message to the Amazon Simple Queue Service (Amazon SQS) queue. Create a fleet of Amazon EC2 instances to pull messages from the SQS queue to process the images and place them in another S3 bucket. Use Amazon CloudWatch metrics for queue depth to scale out EC2 instances. Enable Amazon CloudFront and configure the origin to be the S3 bucket that contains the processed images.
Store the uploaded images on a shared Amazon Elastic Block Store (Amazon EBS) volume mounted to a fleet of Amazon EC2 Spot instances. Create an Amazon DynamoDB table that contains information about each uploaded image and whether it has been processed. Use an Amazon EventBridge rule to scale out EC2 instances. Enable Amazon CloudFront and configure the origin to reference an Elastic Load Balancer in front of the fleet of EC2 instances.

Answer(s): C

Explanation:

C) is the correct choice because it leverages a serverless, scalable architecture that efficiently handles high image upload and processing demand.
-Amazon S3 is ideal for storing the uploaded images.
-S3 bucket event notifications can trigger an event to an Amazon SQS queue when images are uploaded.
-A fleet of Amazon EC2 instances can pull messages from the SQS queue, process the images, and store the processed images in another S3 bucket.
-CloudWatch metrics for the queue depth can be used to auto-scale EC2 instances as the load increases or decreases.
-Amazon CloudFront is used to serve the processed images globally with low latency by configuring the processed image S3 bucket as the origin.
This approach minimizes operational complexity, scales automatically, and leverages AWS managed services effectively.

Reveal Solution Next Question

QUESTION: 287

A company has deployed its database on an Amazon RDS for MySQL DB instance in the us-east-1 Region. The company needs to make its data available to customers in Europe. The customers in Europe must have access to the same data as customers in the United States (US) and will not tolerate high application latency or stale data. The customers in Europe and the customers in the US need to write to the database. Both groups of customers need to see updates from the other group in real time.

Which solution will meet these requirements?

Create an Amazon Aurora MySQL replica of the RDS for MySQL DB instance. Pause application writes to the RDS DB instance. Promote the Aurora Replica to a standalone DB cluster. Reconfigure the application to use the Aurora database and resume writes. Add eu-west-1 as a secondary Region to the DB cluster. Enable write forwarding on the DB cluster. Deploy the application in eu-west-1. Configure the application to use the Aurora MySQL endpoint in eu-west-1.
Add a cross-Region replica in eu-west-1 for the RDS for MySQL DB instance. Configure the replica to replicate write queries back to the primary DB instance. Deploy the application in eu-west-1. Configure the application to use the RDS for MySQL endpoint in eu-west-1.
Copy the most recent snapshot from the RDS for MySQL DB instance to eu-west-1. Create a new RDS for MySQL DB instance in eu-west-1 from the snapshot. Configure MySQL logical replication from us-east-1 to eu-west-1. Enable write forwarding on the DB cluster. Deploy the application in eu-wes&1. Configure the application to use the RDS for MySQL endpoint in eu-west-1.
Convert the RDS for MySQL DB instance to an Amazon Aurora MySQL DB cluster. Add eu-west-1 as a secondary Region to the DB cluster. Enable write forwarding on the DB cluster. Deploy the application in eu-west-1. Configure the application to use the Aurora MySQL endpoint in eu-west-1.

Answer(s): A

Explanation:

A) is the correct solution because it uses Amazon Aurora Global Database with write forwarding. Aurora is designed for low-latency, globally distributed applications with nearly synchronous replication across AWS Regions. This solution provides:
1.Real-time replication across regions, ensuring data consistency and low-latency access for customers in both the US and Europe.
2.Write forwarding enables customers in Europe to send write requests to the primary DB in the US via the European instance, ensuring global data consistency.
3.By promoting the replica to a standalone cluster and adding a secondary Region, the solution ensures high availability and low-latency access.
This architecture meets the requirements of having low latency for European customers and maintaining consistent data updates in real time for both regions.

Reveal Solution Next Question

QUESTION: 288

A company is serving files to its customers through an SFTP server that is accessible over the internet. The SFTP server is running on a single Amazon EC2 instance with an Elastic IP address attached. Customers connect to the SFTP server through its Elastic IP address and use SSH for authentication. The EC2 instance also has an attached security group that allows access from all customer IP addresses.

A solutions architect must implement a solution to improve availability, minimize the complexity of infrastructure management, and minimize the disruption to customers who access files. The solution must not change the way customers connect.

Which solution will meet these requirements?

Disassociate the Elastic IP address from the EC2 instance. Create an Amazon S3 bucket to be used for SFTP file hosting. Create an AWS Transfer Family server. Configure the Transfer Family server with a publicly accessible endpoint. Associate the SFTP Elastic IP address with the new endpoint. Point the Transfer Family server to the S3 bucket. Sync all files from the SFTP server to the S3 bucket.
Disassociate the Elastic IP address from the EC2 instance. Create an Amazon S3 bucket to be used for SFTP file hosting. Create an AWS Transfer Family server. Configure the Transfer Family server with a VPC-hosted, internet-facing endpoint. Associate the SFTP Elastic IP address with the new endpoint. Attach the security group with customer IP addresses to the new endpoint. Point the Transfer Family server to the S3 bucket. Sync all files from the SFTP server to the S3 bucket.
Disassociate the Elastic IP address from the EC2 instance. Create a new Amazon Elastic File System (Amazon EFS) file system to be used for SFTP file hosting. Create an AWS Fargate task definition to run an SFTP server. Specify the EFS file system as a mount in the task definition. Create a Fargate service by using the task definition, and place a Network Load Balancer (NLB) in front of the service. When configuring the service, attach the security group with customer IP addresses to the tasks that run the SFTP server. Associate the Elastic IP address with the NLB. Sync all files from the SFTP server to the S3 bucket.
Disassociate the Elastic IP address from the EC2 instance. Create a multi-attach Amazon Elastic Block Store (Amazon EBS) volume to be used for SFTP file hosting. Create a Network Load Balancer (NLB) with the Elastic IP address attached. Create an Auto Scaling group with EC2 instances that run an SFTP server. Define in the Auto Scaling group that instances that are launched should attach the new multi-attach EBS volume. Configure the Auto Scaling group to automatically add instances behind the NLB. Configure the Auto Scaling group to use the security group that allows customer IP addresses for the EC2 instances that the Auto Scaling group launches. Sync all files from the SFTP server to the new multi-attach EBS volume.

Answer(s): B

Explanation:

B) is the correct solution because it leverages AWS Transfer Family, which provides fully managed SFTP without requiring the use of EC2 instances. By using Transfer Family with an S3 bucket as the backend storage, the company can improve availability and scalability while minimizing the infrastructure management burden.
-No customer disruption: The existing Elastic IP address is associated with the new Transfer Family endpoint, so customers can continue to connect in the same way as before without needing to change their IP whitelists.
-Availability: The S3 bucket ensures high availability and durability of the files.
-Security: The solution uses a VPC-hosted, internet-facing endpoint and attaches the same security group, so customer access controls remain unchanged.
-File Sync: Files are synchronized between the current SFTP server and the new S3 bucket, ensuring continuity.
This approach also eliminates the need for manual EC2 management and provides a robust, scalable, and low-maintenance solution.

Reveal Solution Next Question

Free AWS-SOLUTIONS-ARCHITECT-PROFESSIONAL Exam Braindumps (page: 72)

QUESTION: 285

Explanation:

QUESTION: 286

Explanation:

QUESTION: 287

Explanation:

QUESTION: 288

Explanation: