Here you have the best Amazon SAP-C02 practice exam questions
A company needs to architect a hybrid DNS solution. This solution will use an Amazon Route 53 private hosted zone for the domain cloud.example.com for the resources stored within VPCs.
The company has the following DNS resolution requirements:
On-premises systems should be able to resolve and connect to cloud.example.com.
All VPCs should be able to resolve cloud.example.com.
There is already an AWS Direct Connect connection between the on-premises corporate network and AWS Transit Gateway.
Which architecture should the company use to meet these requirements with the HIGHEST performance?
To achieve the highest performance hybrid DNS solution, the company should associate the Route 53 private hosted zone with all VPCs, ensuring that all VPCs can resolve cloud.example.com. Additionally, creating a Route 53 inbound resolver in the shared services VPC and attaching all VPCs to the transit gateway will allow on-premises systems to resolve the cloud.example.com domain by forwarding rules in the on-premises DNS server pointing to the inbound resolver. This ensures seamless DNS resolution for both on-premises and AWS resources.
A company is providing weather data over a REST-based API to several customers. The API is hosted by Amazon API Gateway and is integrated with different AWS Lambda functions for each API operation. The company uses Amazon Route 53 for DNS and has created a resource record of weather.example.com. The company stores data for the API in Amazon DynamoDB tables. The company needs a solution that will give the API the ability to fail over to a different AWS Region.
Which solution will meet these requirements?
To achieve failover capability for the weather data API, the company should deploy a new API Gateway API and Lambda functions in another AWS Region. The Route 53 DNS record should be changed to a failover record, which allows traffic to be routed to a secondary region if the primary region is unavailable. Enabling target health monitoring ensures that the failover mechanism can detect the health status of the API endpoints and initiate failover when needed. Converting the DynamoDB tables to global tables ensures that the data remains consistent and accessible across multiple regions, allowing the API to function smoothly during a failover event.
A company uses AWS Organizations with a single OU named Production to manage multiple accounts. All accounts are members of the Production OU. Administrators use deny list SCPs in the root of the organization to manage access to restricted services.
The company recently acquired a new business unit and invited the new unit’s existing AWS account to the organization. Once onboarded, the administrators of the new business unit discovered that they are not able to update existing AWS Config rules to meet the company’s policies.
Which option will allow administrators to make changes and continue to enforce the current policies without introducing additional long-term maintenance?
To ensure administrators can update AWS Config rules without introducing long-term maintenance, the best approach would be to create a temporary OU named Onboarding for the new account. Apply an SCP to the Onboarding OU to allow AWS Config actions. Move the organization's root SCP to the Production OU. Once adjustments to AWS Config are complete, the new account can be moved to the Production OU. This method addresses necessary permissions without altering the deny list SCP framework at the root, thereby maintaining the existing security and management protocols across the organization.
A company is running a two-tier web-based application in an on-premises data center. The application layer consists of a single server running a stateful application. The application connects to a PostgreSQL database running on a separate server. The application’s user base is expected to grow significantly, so the company is migrating the application and database to AWS. The solution will use Amazon Aurora PostgreSQL, Amazon EC2 Auto Scaling, and Elastic Load Balancing.
Which solution will provide a consistent user experience that will allow the application and database tiers to scale?
The company needs a solution that can scale both the application and database tiers while providing a consistent user experience. Enabling Aurora Auto Scaling for Aurora Replicas allows the database to scale based on demand by adding or removing read replicas automatically. Using an Application Load Balancer (ALB) with the round robin routing algorithm ensures that incoming traffic is evenly distributed across multiple instances of the application layer, which helps maintain load balance and performance. Enabling sticky sessions ensures that each user's session is maintained with the same backend server, providing a consistent user experience. This combination effectively addresses the requirements of scaling and user session consistency.
A company uses a service to collect metadata from applications that the company hosts on premises. Consumer devices such as TVs and internet radios access the applications. Many older devices do not support certain HTTP headers and exhibit errors when these headers are present in responses. The company has configured an on-premises load balancer to remove the unsupported headers from responses sent to older devices, which the company identified by the User-Agent headers.
The company wants to migrate the service to AWS, adopt serverless technologies, and retain the ability to support the older devices. The company has already migrated the applications into a set of AWS Lambda functions.
Which solution will meet these requirements?
To meet the requirements of migrating the service to AWS, using serverless technologies, and supporting older devices, the best solution involves using an Amazon CloudFront distribution along with a CloudFront function. CloudFront functions are optimized for lightweight tasks like inspecting HTTP headers and modifying requests or responses. This setup allows for efficient removal of problematic headers based on the User-Agent header in the requests, ensuring compatibility with older devices. This approach integrates well with the existing AWS Lambda functions and avoids the need for more complex and potentially costly alternatives like Lambda@Edge or non-serverless components such as an Application Load Balancer.