Free Practice Questions for Amazon Web Services DVA-C02 Exam

Amazon S3 is a service that provides highly scalable, durable, and secure object storage. The developer can create an S3 bucket to host the repository and migrate the existing .xml files to the S3 bucket. The developer can update the application code to use the AWS SDK to read and write configuration files from S3. This solution will meet the requirement of high availability for the repository in a cost-effective way.

Containerization: Packaging the application as a container image promotes portability and standardization. Docker is the standard tool for containerization.

Amazon ECR: ECR is a managed container registry designed to work seamlessly with AWS container services.

Fargate: ECS Fargate provides serverless container orchestration, minimizing operational overhead for this proof-of-concept.

Requirement Summary:

DynamoDBProvisioned Mode

ProvisionedThroughputExceededException error occurring

App hosted on a smallburstable EC2 instance

Option A: Move to a larger EC2 instance

❌May improve local performance, butdoes not solve DynamoDB provisioned throughputlimits.

Option B: Increase DynamoDB RCUs

✅Valid: This directly increases theread throughputcapacity of the table.

Helps handle more traffic andreduce throughput exceptions.

Option C: Reduce frequency via exponential backoff

✅Best practice: Usingexponential backoffandjitterreduces request pressure andspreads retriesout to avoid spiking.

Option D: Increase frequency of retries by reducing delay

❌Opposite of best practice. Increases load, worsening the issue.

Option E: Change to on-demand mode

✅Also validin general, but question is scoped around provisioned capacity.

Sinceminimizing cost or workload typeisn't mentioned, andscaling the existing modelis the focus, prefer B and C.

ProvisionedThroughputExceededException:https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HandlingErrors.html

Exponential backoff:https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Programming.Errors.html

Capacity modes:https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadWriteCapacityMode.html

Why Option A is Correct:Encrypting PII at rest and in transit before storing it in DynamoDB ensures end-to-end security. Using the AWS Database Encryption SDK with KMS keys allows the Lambda function to encrypt data before transmission, meeting security and compliance requirements.

Why Other Options are Incorrect:

Option B:While AWS-managed KMS keys encrypt DynamoDB data at rest, they do not encrypt data in transit.

Option C:DynamoDB streams process updates after the data is written to the table, failing to encrypt PII in transit.

Option D:Step Functions and SQS add unnecessary complexity and still require encryption logic for both transit and at rest.

AWS Documentation References:

Encrypting Data in DynamoDB

AWS Database Encryption SDK

This solution meets the requirements in the most operationally efficient manner because it does not require any infrastructure provisioning or management. The developer can create a Lambda function that makes the API call and configure an EventBridge rule that triggers the function once a day at a designated time. This is a serverless solution that scales automatically and only charges for the execution time of the function.

This benefit occurs when initializing the AWS SDK outside of the Lambda handler function because it allows the SDK instance to be reused across multiple invocations of the same function. This can improve performance and reduce latency by avoiding unnecessary initialization overhead. If the SDK is initialized inside the handler function, it will create a new SDK instance for each invocation, which can increase memory usage and execution time.

CodeDeploy Predefined Configurations: CodeDeploy offers built-in deployment configurations for common scenarios.

Canary Deployment: Canary deployments gradually shift traffic to a new version, ideal for controlled rollouts like this requirement.

CodeDeployDefault.ECSCanary10Percent15Minutes: This configuration matches the company's requirements, shifting 10% of traffic initially and then completing the rollout after 15 minutes.

Problem:Directory access without file names fails.

S3 Static Website Hosting:

Configuring S3 as a static website enables automatic serving of index.html for directory requests.

Bucket policies ensure correct access permissions.

Updating the CloudFront origin simplifies routing.

Avoiding Public Exposure:The S3 website endpoint allows CloudFront to access content without making the bucket public.