Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 69
Question 680
One API Gateway deployment serves test and production stages that use different backend Lambda aliases. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Change only a deployment description and assume backend ARNs update automatically.
- Configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions.
- Treat CloudFront cache invalidation as an integration alias update.
- Test and production invoke the correct Lambda alias without unintended cross-stage traffic.
- Delete all API stages and keep one mutable production endpoint.
Explanation
Correct Answers
B:Configure stage-specific variables or integrations pointing to the intended Lambda alias and grant invoke permissions. This is the concrete implementation required for API Gateway stage variables.
D:Test and production invoke the correct Lambda alias without unintended cross-stage traffic. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Change only a deployment description and assume backend ARNs update automatically. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.
C:Treat CloudFront cache invalidation as an integration alias update. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.
E:Delete all API stages and keep one mutable production endpoint. This is not a suitable implementation or validation step for API Gateway stage variables; it would leave the risk that a hardcoded backend alias in a shared integration can route test traffic into production.
Question 681
A development workstation authenticates an AWS SDK application and must avoid long-lived keys in code. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
- Disable all credential-expiration checks in the SDK.
- Send credentials in query strings to simplify debugging.
- The application authenticates using temporary provider credentials and the repository contains no keys.
- Commit a shared access key in a config JSON file.
Explanation
Correct Answers
A:Use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation. This is the concrete implementation required for temporary credential storage.
D:The application authenticates using temporary provider credentials and the repository contains no keys.
Incorrect Answers
B:Disable all credential-expiration checks in the SDK. This is not a suitable implementation or validation step for temporary credential storage; it would leave the risk that hardcoded long-lived keys can leak through artifacts and remain usable after local sessions end.
C:Send credentials in query strings to simplify debugging. This is not a suitable implementation or validation step for temporary credential storage; it would leave the risk that hardcoded long-lived keys can leak through artifacts and remain usable after local sessions end.
E:Commit a shared access key in a config JSON file. This is not a suitable implementation or validation step for temporary credential storage; it would leave the risk that hardcoded long-lived keys can leak through artifacts and remain usable after local sessions end.
Question 682
A web service downloads private S3 objects that are encrypted using an AWS KMS key. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key.
- Change S3 object metadata without altering key permissions.
- Make the object public to grant KMS Decrypt implicitly.
- Set a cache TTL on CloudFront to override KMS authorization.
- The object can be retrieved and decrypted by the approved principal without broad KMS rights.
Explanation
Correct Answers
A:Ensure the principal has S3 object permission and the required KMS decrypt permission on the encryption key. This is the concrete implementation required for S3 SSE-KMS access.
E:The object can be retrieved and decrypted by the approved principal without broad KMS rights. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
B:Change S3 object metadata without altering key permissions. This is not a suitable implementation or validation step for S3 SSE-KMS access; it would leave the risk that a role allowed to GetObject but denied KMS Decrypt cannot read the plaintext.
C:Make the object public to grant KMS Decrypt implicitly. This is not a suitable implementation or validation step for S3 SSE-KMS access; it would leave the risk that a role allowed to GetObject but denied KMS Decrypt cannot read the plaintext.
D:Set a cache TTL on CloudFront to override KMS authorization. This is not a suitable implementation or validation step for S3 SSE-KMS access; it would leave the risk that a role allowed to GetObject but denied KMS Decrypt cannot read the plaintext.
Question 683
A shared AWS account has several Lambda functions and one bursty worker should not exhaust all available concurrency. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Use CloudFront cache invalidation to reserve Lambda execution slots.
- Set every function reserved concurrency equal to the account total.
- Expect higher Lambda memory alone to impose a safe concurrency cap.
- Function concurrency metrics show the reserved limit applied and other functions retain available capacity.
- Configure reserved concurrency for the critical function at a measured level within account limits.
Explanation
Correct Answers
D:Function concurrency metrics show the reserved limit applied and other functions retain available capacity.
E:Configure reserved concurrency for the critical function at a measured level within account limits. This is the concrete implementation required for Lambda concurrency reservation.
Incorrect Answers
A:Use CloudFront cache invalidation to reserve Lambda execution slots. This is not a suitable implementation or validation step for Lambda concurrency reservation; it would leave the risk that uncontrolled shared concurrency can let a noisy function starve other executions.
B:Set every function reserved concurrency equal to the account total. This is not a suitable implementation or validation step for Lambda concurrency reservation; it would leave the risk that uncontrolled shared concurrency can let a noisy function starve other executions.
C:Expect higher Lambda memory alone to impose a safe concurrency cap. This is not a suitable implementation or validation step for Lambda concurrency reservation; it would leave the risk that uncontrolled shared concurrency can let a noisy function starve other executions.
Question 684
An ECS service unexpectedly runs a different build because the pipeline reuses the mutable latest tag. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Change only the ECS service description without updating task image references.
- Pull latest without recording its digest.
- Pin deployment manifests to an immutable image digest or unique tested release tag.
- The running task image digest matches the tested build artifact after deployment and rollback.
- Rebuild source from the main branch during a rollback.
Explanation
Correct Answers
C:Pin deployment manifests to an immutable image digest or unique tested release tag. This is the concrete implementation required for immutable container image tags.
D:The running task image digest matches the tested build artifact after deployment and rollback. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Change only the ECS service description without updating task image references. This is not a suitable implementation or validation step for immutable container image tags; it would leave the risk that a mutable latest tag can point to different image bytes on separate deployments.
B:Pull latest without recording its digest. This is not a suitable implementation or validation step for immutable container image tags; it would leave the risk that a mutable latest tag can point to different image bytes on separate deployments.
E:Rebuild source from the main branch during a rollback. This is not a suitable implementation or validation step for immutable container image tags; it would leave the risk that a mutable latest tag can point to different image bytes on separate deployments.
Question 685
A staging application needs encrypted configuration parameters with controlled IAM/KMS access. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Authorized reads with decryption return the intended value while unauthorized callers cannot decrypt it.
- Store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval.
- Store the encrypted string and its decryption key together in a public README.
- Put the secret in a plain CloudFormation output without protection.
- Print parameter contents to every startup log.
Explanation
Correct Answers
A:Authorized reads with decryption return the intended value while unauthorized callers cannot decrypt it.
B:Store the parameter as an SSM Parameter Store SecureString with KMS protection and restricted retrieval. This is the concrete implementation required for Parameter Store secure strings.
Incorrect Answers
C:Store the encrypted string and its decryption key together in a public README. This is not a suitable implementation or validation step for Parameter Store secure strings; it would leave the risk that a plaintext String parameter does not provide the intended encrypted-at-rest secret boundary.
D:Put the secret in a plain CloudFormation output without protection. This is not a suitable implementation or validation step for Parameter Store secure strings; it would leave the risk that a plaintext String parameter does not provide the intended encrypted-at-rest secret boundary.
E:Print parameter contents to every startup log. This is not a suitable implementation or validation step for Parameter Store secure strings; it would leave the risk that a plaintext String parameter does not provide the intended encrypted-at-rest secret boundary.
Question 686
A serverless deployment changes Lambda resource properties and needs predeploy checks. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Template validation catches syntactic and supported structural IaC problems but not all runtime behavior.
- Increase Lambda memory to make CloudFormation parse invalid syntax.
- Change a Git branch name to repair invalid YAML.
- Invalid resource declarations fail the validation stage before stack mutation.
- Run sam validate and template linting before packaging and deploying the application.
- Replace SAM validation with an HTTP request to the production API.
Explanation
Correct Answers
A:Template validation catches syntactic and supported structural IaC problems but not all runtime behavior. This states the AWS behavior that makes the implementation valid.
D:Invalid resource declarations fail the validation stage before stack mutation. This is the workload-specific evidence needed to validate the change.
E:Run sam validate and template linting before packaging and deploying the application. This is the concrete implementation required for SAM template validation.
Incorrect Answers
B:Increase Lambda memory to make CloudFormation parse invalid syntax. This is not a suitable implementation or validation step for SAM template validation; it would leave the risk that a malformed template can fail deployment even if application unit tests pass.
C:Change a Git branch name to repair invalid YAML. This is not a suitable implementation or validation step for SAM template validation; it would leave the risk that a malformed template can fail deployment even if application unit tests pass.
F:Replace SAM validation with an HTTP request to the production API. This is not a suitable implementation or validation step for SAM template validation; it would leave the risk that a malformed template can fail deployment even if application unit tests pass.
Question 687
An order API adds an optional field and must not break older mobile clients. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Skip compatibility checks because the code compiles.
- Older client fixtures and the revised contract both pass against the candidate API stage.
- Run consumer contract tests across supported API versions and stage new behavior before promotion.
- Change the certificate expiry date to repair JSON schema compatibility.
- Rename all response fields to match the newest client only.
Explanation
Correct Answers
B:Older client fixtures and the revised contract both pass against the candidate API stage. This is the workload-specific evidence needed to validate the change.
C:Run consumer contract tests across supported API versions and stage new behavior before promotion. This is the concrete implementation required for contract testing versioned API.
Incorrect Answers
A:Skip compatibility checks because the code compiles. This is not a suitable implementation or validation step for contract testing versioned API; it would leave the risk that changing required response shapes without consumer tests can break callers after deployment.
D:Change the certificate expiry date to repair JSON schema compatibility. This is not a suitable implementation or validation step for contract testing versioned API; it would leave the risk that changing required response shapes without consumer tests can break callers after deployment.
E:Rename all response fields to match the newest client only. This is not a suitable implementation or validation step for contract testing versioned API; it would leave the risk that changing required response shapes without consumer tests can break callers after deployment.
Question 688
An API Gateway route produces 504 responses when an upstream Lambda call takes too long. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Add random retries to the front end with no timeout diagnosis.
- End-to-end traces show the integration completes under the configured limit without gateway timeouts.
- Set the Lambda function timeout to fifteen minutes and assume API Gateway waits equally long.
- Measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit.
- Increase DynamoDB TTL to change HTTP integration deadlines.
Explanation
Correct Answers
B:End-to-end traces show the integration completes under the configured limit without gateway timeouts.
D:Measure the integration latency and redesign or optimize synchronous work to finish within the API integration limit. This is the concrete implementation required for API Gateway Lambda integration timeout.
Incorrect Answers
A:Add random retries to the front end with no timeout diagnosis. This is not a suitable implementation or validation step for API Gateway Lambda integration timeout; it would leave the risk that a longer Lambda timeout alone does not prevent an earlier API Gateway integration timeout.
C:Set the Lambda function timeout to fifteen minutes and assume API Gateway waits equally long. This is not a suitable implementation or validation step for API Gateway Lambda integration timeout; it would leave the risk that a longer Lambda timeout alone does not prevent an earlier API Gateway integration timeout.
E:Increase DynamoDB TTL to change HTTP integration deadlines. This is not a suitable implementation or validation step for API Gateway Lambda integration timeout; it would leave the risk that a longer Lambda timeout alone does not prevent an earlier API Gateway integration timeout.
Question 689
A mobile client needs temporary upload access to one object key without AWS credentials. Select THREE statements that together form a sound implementation and validation plan for this requirement.
- Presigned requests delegate bounded use of the signing principal's permissions without exposing long-lived keys.
- Embed an IAM user's permanent secret access key in mobile apps.
- Generate a scoped presigned S3 URL with the intended method, object key, and expiration.
- Make the entire bucket publicly writable.
- Use an unsigned GET URL for a private PUT upload.
- A request succeeds before expiry for the intended action and fails after the URL is invalid.
Explanation
Correct Answers
A:Presigned requests delegate bounded use of the signing principal's permissions without exposing long-lived keys. This states the AWS behavior that makes the implementation valid.
C:Generate a scoped presigned S3 URL with the intended method, object key, and expiration. This is the concrete implementation required for S3 presigned URLs.
F:A request succeeds before expiry for the intended action and fails after the URL is invalid. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
B:Embed an IAM user's permanent secret access key in mobile apps. This is not a suitable implementation or validation step for S3 presigned URLs; it would leave the risk that publishing access keys in client code exposes reusable credentials beyond one object operation.
D:Make the entire bucket publicly writable. This is not a suitable implementation or validation step for S3 presigned URLs; it would leave the risk that publishing access keys in client code exposes reusable credentials beyond one object operation.
E:Use an unsigned GET URL for a private PUT upload. This is not a suitable implementation or validation step for S3 presigned URLs; it would leave the risk that publishing access keys in client code exposes reusable credentials beyond one object operation.
Question 690
A Lambda producer invokes an internal Lambda consumer and must avoid shared static API keys. Select TWO statements that together form a sound implementation and validation plan for this requirement.
- Treat a browser-supplied user ID as an AWS service principal.
- Use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required.
- Place a permanent admin API key in both Lambda source files.
- Make every target endpoint publicly invokable to avoid IAM trust.
- CloudTrail and target logs show requests authorized only for the permitted source principal.
Explanation
Correct Answers
B:Use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required. This is the concrete implementation required for service-to-service IAM authorization.
E:CloudTrail and target logs show requests authorized only for the permitted source principal. This is the workload-specific evidence needed to validate the change.
Incorrect Answers
A:Treat a browser-supplied user ID as an AWS service principal. This is not a suitable implementation or validation step for service-to-service IAM authorization; it would leave the risk that a backend-to-backend call can fail when identity access exists but a required resource policy denies the principal.
C:Place a permanent admin API key in both Lambda source files. This is not a suitable implementation or validation step for service-to-service IAM authorization; it would leave the risk that a backend-to-backend call can fail when identity access exists but a required resource policy denies the principal.
D:Make every target endpoint publicly invokable to avoid IAM trust. This is not a suitable implementation or validation step for service-to-service IAM authorization; it would leave the risk that a backend-to-backend call can fail when identity access exists but a required resource policy denies the principal.