{"id":18792,"date":"2026-09-22T10:02:53","date_gmt":"2026-09-22T10:02:53","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=18792"},"modified":"2026-09-22T10:02:53","modified_gmt":"2026-09-22T10:02:53","slug":"amazon-aws-certified-developer-associate-dva-c02-practice-test-questions-and-exam-dumps-part10-q181-200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/amazon-aws-certified-developer-associate-dva-c02-practice-test-questions-and-exam-dumps-part10-q181-200\/","title":{"rendered":"Amazon AWS Certified Developer &#8211; Associate DVA-C02 Practice Test Questions and Exam Dumps Part10 Q181-200"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/aws-certified-developer-associate-dva-c02-exam-dumps\"><b>Amazon AWS Certified Developer &#8211; Associate DVA-C02 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 181<\/b><\/h3>\n<p><b>A developer needs to execute a workflow that contains several AWS service calls and requires branching based on the result of previous steps. Which AWS service should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon S3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SNS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SQS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Step Functions<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Step Functions is designed to coordinate multiple steps in an application workflow. A state machine can call AWS services, invoke Lambda functions, wait for results, retry failed operations, and branch based on conditions. This makes Step Functions useful for workflows that contain several dependent operations or require explicit orchestration. S3 provides object storage, SNS provides pub\/sub messaging, and SQS provides message queuing. Step Functions can also maintain workflow state and provide execution history, making it easier to understand and troubleshoot complex application processes. It is therefore appropriate for orchestrating multi-step AWS application workflows.<\/span><\/p>\n<h3><b>Question 182<\/b><\/h3>\n<p><b>A developer needs to store application configuration values that are not highly sensitive and retrieve them at runtime. Which service is appropriate?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS Systems Manager Parameter Store<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon CloudFront<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ECR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Kinesis Data Firehose<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Systems Manager Parameter Store provides centralized storage for configuration values and parameters. Applications can retrieve these values at runtime rather than embedding configuration directly in source code. Parameter Store supports different parameter types and can integrate with AWS services and IAM permissions. It is useful for storing values such as environment-specific settings, service endpoints, and feature configuration. Highly sensitive values can also be stored using secure string parameters, although Secrets Manager provides additional secret-management and rotation capabilities. CloudFront, ECR, and Kinesis Data Firehose serve different purposes and are not designed primarily for centralized application configuration.<\/span><\/p>\n<h3><b>Question 183<\/b><\/h3>\n<p><b>A Lambda function is receiving more concurrent requests than expected. The developer wants to guarantee that the function does not consume more than a specific number of concurrent executions. Which feature should be configured?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provisioned concurrency<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reserved concurrency<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda layer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Function URL<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Reserved concurrency establishes a dedicated concurrency limit for a Lambda function. It prevents that function from using more than the configured number of concurrent executions and can also reserve capacity for the function. This is useful when developers need to protect downstream systems from excessive traffic or prevent one function from consuming the account&#8217;s available concurrency. Provisioned concurrency serves a different purpose by keeping execution environments initialized to reduce startup latency. Lambda layers package reusable dependencies, while function URLs provide HTTP endpoints. Reserved concurrency is therefore the appropriate feature for enforcing a maximum concurrency limit.<\/span><\/p>\n<h3><b>Question 184<\/b><\/h3>\n<p><b>A developer wants to reduce cold-start latency for a latency-sensitive Lambda function. Which feature should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reserved concurrency<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dead-letter queue<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provisioned concurrency<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 lifecycle configuration<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Lambda Provisioned Concurrency keeps a specified number of execution environments initialized and ready to respond to requests. This can reduce cold-start latency for workloads where predictable response times are important. It is particularly useful for interactive APIs and other latency-sensitive applications. Reserved concurrency controls the maximum and reserved concurrent execution capacity but does not itself keep environments initialized. Dead-letter queues are related to failed asynchronous processing, while S3 lifecycle configurations manage object storage. Provisioned concurrency is therefore the appropriate Lambda feature when the primary objective is reducing initialization latency for incoming requests.<\/span><\/p>\n<h3><b>Question 185<\/b><\/h3>\n<p><b>A developer wants to encrypt application data using a customer-controlled encryption key and manage permissions for using that key. Which AWS service should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SQS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon CloudWatch<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS KMS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Route 53<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS Key Management Service, or KMS, provides managed cryptographic keys that applications and AWS services can use to encrypt and decrypt data. Developers can control access to customer managed KMS keys through IAM policies and key policies. KMS integrates with many AWS services, allowing encryption to be managed centrally. SQS provides messaging, CloudWatch provides monitoring, and Route 53 provides DNS functionality. When an application requires controlled encryption-key management and authorization over key usage, KMS is the appropriate service. Developers should also follow least-privilege principles when granting applications permission to use encryption keys.<\/span><\/p>\n<h3><b>Question 186<\/b><\/h3>\n<p><b>A developer is building a serverless application and wants to package reusable libraries separately from the Lambda function code. Which feature should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda layers<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda destinations<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda aliases<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda event source mappings<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Lambda layers allow developers to package libraries, dependencies, custom runtimes, or other reusable components separately from the main function deployment package. Multiple Lambda functions can reference the same layer, which can simplify dependency management and reduce duplicated packaging work. Lambda destinations configure where asynchronous invocation results are sent, aliases provide named references to function versions, and event source mappings connect Lambda to supported event sources. Layers are therefore useful when several functions need common dependencies or shared code. Developers should manage layer versions carefully so that functions use the intended dependency versions.<\/span><\/p>\n<h3><b>Question 187<\/b><\/h3>\n<p><b>A developer wants an application to consume records from Kinesis Data Streams using Lambda. What should be configured?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">API Gateway integration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda event source mapping<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CloudFront distribution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 lifecycle rule<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Lambda event source mapping can connect a Lambda function to Kinesis Data Streams. Lambda reads records from the stream and invokes the function with batches of records according to the configured event source settings. This enables serverless stream processing without requiring the developer to continuously poll Kinesis manually. API Gateway is used primarily for exposing HTTP APIs, CloudFront provides content delivery, and S3 lifecycle rules manage object retention. Event source mapping is therefore the appropriate integration when Lambda needs to consume and process records from Kinesis Data Streams.<\/span><\/p>\n<h3><b>Question 188<\/b><\/h3>\n<p><b>A developer wants to prevent an application from repeatedly processing the same SQS message after a successful operation. Which approach is most appropriate?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increase message size<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable visibility timeout<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delete the message after successful processing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Move every message to a dead-letter queue<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">After an SQS message has been successfully processed, the consumer should delete the message from the queue. If the message is not deleted before the visibility timeout expires, SQS can make it visible again for another consumer or processing attempt. Deleting the message after successful processing prevents the same message from remaining in the queue. Applications should also be designed to tolerate duplicate delivery because distributed systems can still encounter retry scenarios. Increasing message size or disabling visibility timeout does not solve this problem, and sending every message to a dead-letter queue would be incorrect.<\/span><\/p>\n<h3><b>Question 189<\/b><\/h3>\n<p><b>A developer wants to automatically deploy a new application version to a small percentage of Lambda traffic before increasing the traffic gradually. Which deployment approach can be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 versioning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB Streams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda alias with weighted routing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SQS FIFO ordering<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Lambda aliases can point to function versions, and weighted alias routing can distribute traffic between two versions. This enables deployment strategies where a small percentage of requests are sent to a new version before traffic is gradually increased. Such an approach can reduce deployment risk by allowing developers to observe application behavior before directing all traffic to the new version. S3 versioning manages object versions, DynamoDB Streams captures table changes, and SQS FIFO provides ordered messaging. Weighted Lambda alias routing is therefore useful for controlled gradual deployments between Lambda function versions.<\/span><\/p>\n<h3><b>Question 190<\/b><\/h3>\n<p><b>A developer needs to create a temporary URL that allows a client to upload an object directly to a private S3 bucket. Which mechanism should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Public bucket policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 presigned URL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root access key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CloudFront invalidation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An S3 presigned URL allows a client to perform a specific S3 operation for a limited period without receiving permanent AWS credentials. A developer can generate a presigned URL for uploading an object to a private bucket and specify an expiration time. This approach is useful for browser and mobile applications where the client should upload directly to S3 without exposing AWS credentials. Making the bucket public unnecessarily broadens access, while root credentials should never be distributed to applications or clients. CloudFront invalidation is unrelated to generating temporary upload authorization.<\/span><\/p>\n<h3><b>Question 191<\/b><\/h3>\n<p><b>A developer wants to automatically remove expired items from a DynamoDB table without writing a scheduled cleanup process. Which feature should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB Streams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB TTL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Global secondary index<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BatchWriteItem<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">DynamoDB Time to Live, or TTL, allows developers to mark items for expiration by storing a designated timestamp attribute. DynamoDB automatically removes expired items after the TTL process determines that they are eligible for deletion. This is useful for temporary data such as session records, cached information, and short-lived application state. DynamoDB Streams captures item-level changes, global secondary indexes support additional query patterns, and BatchWriteItem performs batch write or delete operations. TTL removes the need for developers to build a separate scheduled process solely for deleting expired records.<\/span><\/p>\n<h3><b>Question 192<\/b><\/h3>\n<p><b>A developer wants to receive notifications when a CloudWatch alarm enters the ALARM state. Which service can be used as the notification target?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SNS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ECR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon RDS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon DynamoDB<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Amazon SNS can receive notifications from CloudWatch alarms and distribute them to subscribed endpoints. For example, an SNS topic can deliver notifications through supported protocols or integrate with other AWS services. A CloudWatch alarm evaluates a metric against a configured threshold and changes state when the condition is met. SNS then provides the notification and fanout mechanism. ECR manages container images, RDS provides relational databases, and DynamoDB provides NoSQL storage. Using CloudWatch alarms together with SNS is a common way to notify application or operations teams about monitored conditions.<\/span><\/p>\n<h3><b>Question 193<\/b><\/h3>\n<p><b>A developer needs to upload a very large file to Amazon S3 efficiently and wants to upload different portions independently. Which S3 feature should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Object Lock<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Select<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multipart upload<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 Inventory<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">S3 multipart upload divides a large object into multiple parts that can be uploaded independently and potentially in parallel. This can improve upload performance and provide better recovery because failed parts can be retried without restarting the entire upload. After all required parts are uploaded, S3 assembles them into the final object. Object Lock is used for retention protection, S3 Select retrieves selected data from supported objects, and S3 Inventory provides object listings and metadata reports. Multipart upload is therefore appropriate for efficiently transferring large objects to Amazon S3.<\/span><\/p>\n<h3><b>Question 194<\/b><\/h3>\n<p><b>A developer wants to trace requests as they move through API Gateway and Lambda to identify latency and service dependencies. Which AWS service should be considered?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon S3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS X-Ray<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ECR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon Route 53<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">AWS X-Ray helps developers analyze and trace requests as they move through distributed applications. It can provide information about service calls, latency, errors, and dependencies across supported AWS services and application components. This is particularly useful in microservice and serverless architectures where a single user request can involve multiple services. S3 provides object storage, ECR stores container images, and Route 53 provides DNS services. X-Ray is therefore useful when developers need distributed tracing information to identify performance bottlenecks and understand how requests travel through an application.<\/span><\/p>\n<h3><b>Question 195<\/b><\/h3>\n<p><b>A developer wants to configure an API Gateway endpoint so that excessive client requests are limited. Which feature should be configured?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">API Gateway throttling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">S3 versioning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB TTL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lambda layers<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">API Gateway throttling limits the rate at which requests can be processed by an API. This helps protect backend services from excessive traffic and can prevent a sudden increase in requests from overwhelming downstream resources. Throttling can be configured at different levels depending on the API type and requirements. S3 versioning maintains multiple object versions, DynamoDB TTL handles automatic expiration of items, and Lambda layers package reusable dependencies. API Gateway throttling is therefore the appropriate mechanism when a developer needs to control request rates and protect an API backend from excessive traffic.<\/span><\/p>\n<h3><b>Question 196<\/b><\/h3>\n<p><b>A developer wants an application to receive a stream of database changes from DynamoDB whenever items are created, updated, or deleted. Which feature should be enabled?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB Streams<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB TTL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB Accelerator only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DynamoDB table encryption<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">DynamoDB Streams captures item-level modifications in a DynamoDB table. Depending on the configured stream view type, the stream can provide information about new and old item images and keys associated with changes. Applications can consume these records for event-driven processing, auditing workflows, replication-related processes, and other use cases. TTL automatically expires items, caching services improve read performance, and encryption protects stored data. DynamoDB Streams is therefore the appropriate feature when an application needs to react to changes made to DynamoDB items.<\/span><\/p>\n<h3><b>Question 197<\/b><\/h3>\n<p><b>A developer wants to store a Docker container image that will later be deployed to Amazon ECS. Which AWS service should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SQS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ECR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon SNS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon CloudWatch<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Amazon Elastic Container Registry, or ECR, is a managed container image registry. Developers can push Docker and other OCI-compatible container images to ECR and configure ECS tasks to retrieve those images during deployment or startup. ECR integrates with IAM and other AWS services to control access to container images. SQS provides message queuing, SNS provides pub\/sub messaging, and CloudWatch provides monitoring and logging capabilities. ECR is therefore the appropriate AWS service for storing and managing container images that will be used by ECS workloads.<\/span><\/p>\n<h3><b>Question 198<\/b><\/h3>\n<p><b>A developer needs to store objects with automatic encryption using an AWS managed key. Which S3 encryption option can be selected?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SSE-S3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client-side encryption only<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Plaintext object storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">No encryption configuration<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SSE-S3 provides server-side encryption for S3 objects using keys managed by Amazon S3. It allows objects to be encrypted at rest without requiring the application to implement its own encryption process. Developers can select other encryption approaches, such as SSE-KMS, when they need additional key-management controls and KMS integration. Client-side encryption requires the application to encrypt data before sending it to S3. Storing sensitive data without encryption is generally inappropriate when encryption at rest is required. SSE-S3 is therefore an appropriate option when standard S3-managed server-side encryption is sufficient.<\/span><\/p>\n<h3><b>Question 199<\/b><\/h3>\n<p><b>A developer wants to process messages from an SQS queue while minimizing the number of empty ReceiveMessage requests. Which feature should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Message groups<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Long polling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object versioning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">API caching<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SQS long polling allows a ReceiveMessage request to wait for messages to become available instead of immediately returning an empty response when the queue has no messages. This can reduce the number of empty receive requests and lower unnecessary request activity. Long polling can be configured through the receive wait time and is useful for consumers that continuously poll SQS. Message groups are associated with FIFO ordering, object versioning is an S3 feature, and API caching is unrelated to SQS consumption. Long polling is therefore appropriate when developers want more efficient message retrieval from an SQS queue.<\/span><\/p>\n<h3><b>Question 200<\/b><\/h3>\n<p><b>A developer wants to store frequently accessed database results in memory to reduce database load and improve application response times. Which AWS service is designed for this purpose?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon CloudTrail<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon EventBridge<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Amazon ElastiCache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AWS CloudFormation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Amazon ElastiCache provides managed in-memory data stores that can be used to cache frequently accessed application data. By storing commonly requested results in memory, an application can reduce repeated database queries and improve response times. This is especially useful for read-heavy workloads where the same data is requested frequently. CloudTrail records API activity, EventBridge routes events, and CloudFormation manages infrastructure as code. ElastiCache is therefore appropriate when an application needs a low-latency caching layer between the application and its primary data store.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Amazon AWS Certified Developer &#8211; Associate DVA-C02 Exam Dumps and Practice Test Dumps. &nbsp; Question 181 A developer needs to execute a workflow that contains several AWS service calls and requires branching based on the result of previous steps. Which AWS service should be used? Amazon S3 Amazon SNS Amazon SQS AWS Step [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18792"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=18792"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18792\/revisions"}],"predecessor-version":[{"id":18793,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18792\/revisions\/18793"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=18792"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=18792"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=18792"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}