AWS Certified Associate SOA-C02 Exam Questions and Answers PDF

Adding a Route to the Route Tables:

When new subnets are created, they need appropriate routing to ensure communication with on-premises networks.

Steps:

Go to the AWS Management Console.

Navigate to VPC.

Select the route table associated with the new subnets.

Choose "Edit routes."

Add a new route with the destination CIDR block of the on-premises network.

For the target, select the virtual private gateway (VGW).

This ensures that traffic destined for the on-premises network is routed correctly through the VPN connection.

AWS Storage Gateway provides a hybrid cloud storage service that enables on-premises applications to seamlessly use AWS cloud storage. The gateway-stored volumes configuration is suitable for scenarios where all data must be available locally and the backup application can write only to block-based storage that is POSIX-compliant.

Deploy AWS Storage Gateway:

Launch the AWS Storage Gateway service from the AWS Management Console.

Download and deploy the Storage Gateway VM on your on-premises infrastructure.

Activate the Gateway:

Activate the Storage Gateway by connecting it to your AWS account.

Follow the setup wizard to complete the activation process.

Configure Gateway-Stored Volumes:

Create a gateway-stored volume where the primary data is stored locally, and an asynchronous copy is stored in AWS.

Specify the size of the volume and configure it to match your backup application's requirements.

Connect the Backup Application:

Present the created volume to your on-premises backup application as an iSCSI target.

Configure the backup application to write data to the iSCSI target provided by the Storage Gateway.

Monitor and Manage:

Use the AWS Management Console to monitor the gateway and the volumes.

Ensure that the data is being backed up to AWS correctly and that local copies are maintained as required.

References:

AWS Storage Gateway User Guide

Gateway-Stored Volumes

To optimize the cost of a workload running in multiple AWS Regions using AWS Lambda and EC2 On-Demand Instances, the SysOps administrator should purchase Compute Savings Plans based on the usage during the past 30 days.

Compute Savings Plans:

Compute Savings Plans provide the most flexibility and can be applied across various compute services such as EC2, AWS Lambda, and Fargate.

They offer significant savings compared to On-Demand pricing.

Analysis and Purchase:

Analyze the compute usage over the past 30 days to determine the baseline usage.

Purchase Compute Savings Plans based on this baseline to maximize savings while maintaining flexibility across different regions and compute services.

Amazon FSx for Windows File Server provides a fully managed, highly available, and native Windows file system compatible with the SMB protocol, ideal for Windows workloads requiring shared access.

Multi-AZ File System: Ensures high availability across multiple Availability Zones.

Native Windows Capabilities: Allows instances to map file shares and access files using Windows storage features, offering strong consistency and performance for shared files.

Other options, like Amazon S3 and Amazon EFS, either lack native Windows integration or do not offer the desired consistency and high availability for shared file systems in a Windows environment.