Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 36
Question 350
An internal API returns user objects and needs role-specific masking of email and national identifiers. A teammate asks why the proposed PII response field masking approach is technically appropriate. Which AWS behavior BEST explains the decision?
- KMS-managed rotation retains key identity and the old material required to decrypt previous ciphertext.
- Cross-account KMS use needs key-policy authorization in the owning account and corresponding caller permissions.
- A tenant identifier from verified claims must control data scoping instead of untrusted request parameters.
- Response masking and field authorization must run before data is returned to a caller.
Explanation
Correct Answer
D:Response masking and field authorization must run before data is returned to a caller. This is the governing behavior behind the recommended change: apply field-level authorization and mask sensitive attributes before serializing responses.
Incorrect Answers
A:The statement describes KMS rotation scope, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.
B:The statement describes KMS key-policy cross-account, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.
C:The statement describes multi-tenant DynamoDB row isolation, which is not the controlling AWS behavior for this PII response field masking situation. The required implementation is: apply field-level authorization and mask sensitive attributes before serializing responses.
Question 351
A team needs repeatable local invocation of SAM-defined handlers using saved JSON events. A teammate asks why the proposed local SAM API testing approach is technically appropriate. Which AWS behavior BEST explains the decision?
- IaC tracks declared infrastructure; out-of-band console edits can cause state divergence.
- Lambda versions snapshot function code and configuration; aliases provide movable references.
- Generated tests require human review and meaningful assertions to avoid false confidence.
- SAM local testing helps validate handler behavior before a cloud deployment but does not replace all integration tests.
Explanation
Correct Answer
D:SAM local testing helps validate handler behavior before a cloud deployment but does not replace all integration tests. This is the governing behavior behind the recommended change: run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.
Incorrect Answers
A:The statement describes infrastructure drift detection, which is not the controlling AWS behavior for this local SAM API testing situation. The required implementation is: run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.
B:The statement describes Lambda alias version testing, which is not the controlling AWS behavior for this local SAM API testing situation. The required implementation is: run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.
C:The statement describes AI-assisted test review, which is not the controlling AWS behavior for this local SAM API testing situation. The required implementation is: run AWS SAM CLI local API or invoke tests with representative events and runtime-compatible containers.
Question 352
A service caches an API token and must recover promptly when that token is rotated. A teammate asks why the proposed credential caching refresh approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Bounded secret caching reduces repeated retrieval without making old credentials permanent.
- AWS service-to-service calls use IAM identity and resource permissions according to API requirements.
- A tenant identifier from verified claims must control data scoping instead of untrusted request parameters.
- Client-side encryption protects data prior to upload; SSE encrypts it after S3 receives the request.
Explanation
Correct Answer
A:Bounded secret caching reduces repeated retrieval without making old credentials permanent. This is the governing behavior behind the recommended change: cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access.
Incorrect Answers
B:The statement describes service-to-service IAM authorization, which is not the controlling AWS behavior for this credential caching refresh situation. The required implementation is: cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access.
C:The statement describes multi-tenant DynamoDB row isolation, which is not the controlling AWS behavior for this credential caching refresh situation. The required implementation is: cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access.
D:The statement describes client-side versus server-side encryption, which is not the controlling AWS behavior for this credential caching refresh situation. The required implementation is: cache secrets for a bounded interval and refresh on expiry or authentication failure using least-privilege access.
Question 353
An ECS workload pulls an image built only for a CPU platform the target tasks do not support. A teammate asks why the proposed container image architecture compatibility approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Lambda versions snapshot function code and configuration; aliases provide movable references.
- Explicit test fixtures make regression behavior reproducible across deployments.
- CPU architecture and container-image manifests must match the target runtime.
- Configuration releases can be separated from binary releases with validators and deployment controls.
Explanation
Correct Answer
C:CPU architecture and container-image manifests must match the target runtime. This is the governing behavior behind the recommended change: build and publish a container image for the target runtime platform and set compatible deployment architecture.
Incorrect Answers
A:The statement describes Lambda alias version testing, which is not the controlling AWS behavior for this container image architecture compatibility situation. The required implementation is: build and publish a container image for the target runtime platform and set compatible deployment architecture.
B:The statement describes deployment test event generation, which is not the controlling AWS behavior for this container image architecture compatibility situation. The required implementation is: build and publish a container image for the target runtime platform and set compatible deployment architecture.
D:The statement describes environment-specific AppConfig, which is not the controlling AWS behavior for this container image architecture compatibility situation. The required implementation is: build and publish a container image for the target runtime platform and set compatible deployment architecture.
Question 354
A production application rotates a certificate on a load-balanced HTTPS endpoint without a plaintext fallback. A teammate asks why the proposed TLS certificate rotation ACM approach is technically appropriate. Which AWS behavior BEST explains the decision?
- SSE-KMS authorization involves both S3 API access and KMS cryptographic authorization.
- Cognito identity pools broker temporary AWS credentials for supported identity providers.
- TLS certificates authenticate endpoint names and protect traffic in transit.
- Cognito user pools handle user sign-in and tokens, while identity pools serve temporary AWS credentials.
Explanation
Correct Answer
C:TLS certificates authenticate endpoint names and protect traffic in transit. This is the governing behavior behind the recommended change: provision and validate the certificate using AWS Certificate Manager and associate the renewed certificate with the endpoint.
Incorrect Answers
A:The statement describes S3 SSE-KMS access, which is not the controlling AWS behavior for this TLS certificate rotation ACM situation. The required implementation is: provision and validate the certificate using AWS Certificate Manager and associate the renewed certificate with the endpoint.
B:The statement describes Cognito identity pool AWS access, which is not the controlling AWS behavior for this TLS certificate rotation ACM situation. The required implementation is: provision and validate the certificate using AWS Certificate Manager and associate the renewed certificate with the endpoint.
D:The statement describes Cognito user pool authentication, which is not the controlling AWS behavior for this TLS certificate rotation ACM situation. The required implementation is: provision and validate the certificate using AWS Certificate Manager and associate the renewed certificate with the endpoint.
Question 355
A user edits a profile and the next request must see the committed change on the base table. A teammate asks why the proposed DynamoDB strong read consistency approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs.
- AI coding suggestions accelerate development but do not replace validation or security review.
- DynamoDB partition-key choice influences physical request distribution and hot-key throttling.
- Circuit breakers limit cascading latency while allowing controlled recovery after dependency outages.
Explanation
Correct Answer
A:Strongly consistent reads are available on DynamoDB tables and LSIs in a Region, not GSIs. This is the governing behavior behind the recommended change: request a strongly consistent read for the DynamoDB table or LSI where supported.
Incorrect Answers
B:The statement describes Amazon Q Developer review, which is not the controlling AWS behavior for this DynamoDB strong read consistency situation. The required implementation is: request a strongly consistent read for the DynamoDB table or LSI where supported.
C:The statement describes DynamoDB partition key cardinality, which is not the controlling AWS behavior for this DynamoDB strong read consistency situation. The required implementation is: request a strongly consistent read for the DynamoDB table or LSI where supported.
D:The statement describes third-party circuit breaker, which is not the controlling AWS behavior for this DynamoDB strong read consistency situation. The required implementation is: request a strongly consistent read for the DynamoDB table or LSI where supported.
Question 356
One AWS service integration needs scoped authority to publish to a different service in the same account. A teammate asks why the proposed service-to-service IAM authorization approach is technically appropriate. Which AWS behavior BEST explains the decision?
- AWS service-to-service calls use IAM identity and resource permissions according to API requirements.
- Bounded secret caching reduces repeated retrieval without making old credentials permanent.
- An explicit Deny takes precedence over any applicable Allow in AWS policy evaluation.
- Envelope encryption uses a data key for payload encryption and protects that key using a KMS key.
Explanation
Correct Answer
A:AWS service-to-service calls use IAM identity and resource permissions according to API requirements. This is the governing behavior behind the recommended change: use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required.
Incorrect Answers
B:The statement describes credential caching refresh, which is not the controlling AWS behavior for this service-to-service IAM authorization situation. The required implementation is: use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required.
C:The statement describes IAM policy explicit deny, which is not the controlling AWS behavior for this service-to-service IAM authorization situation. The required implementation is: use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required.
D:The statement describes KMS envelope encryption, which is not the controlling AWS behavior for this service-to-service IAM authorization situation. The required implementation is: use IAM-authenticated AWS SDK calls with a narrowly scoped identity policy and resource policy when required.
Question 357
A queue worker should test batch partial failure outputs before a production release. A teammate asks why the proposed SQS handler contract tests approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Event-driven tests must exercise the actual source envelope and partial failure contract.
- Configuration releases can be separated from binary releases with validators and deployment controls.
- Mocks isolate code logic while independent integration checks validate real API contracts.
- IaC tracks declared infrastructure; out-of-band console edits can cause state divergence.
Explanation
Correct Answer
A:Event-driven tests must exercise the actual source envelope and partial failure contract. This is the governing behavior behind the recommended change: build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
Incorrect Answers
B:The statement describes environment-specific AppConfig, which is not the controlling AWS behavior for this SQS handler contract tests situation. The required implementation is: build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
C:The statement describes API external dependency mocks, which is not the controlling AWS behavior for this SQS handler contract tests situation. The required implementation is: build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
D:The statement describes infrastructure drift detection, which is not the controlling AWS behavior for this SQS handler contract tests situation. The required implementation is: build test events using realistic SQS Records metadata and verify handler output plus failure identifiers.
Question 358
A CDN caches a public product listing that differs according to a small set of approved request headers. A teammate asks why the proposed API response caching variation approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Concurrency controls must reflect downstream capacity rather than only upstream invocation volume.
- Trace propagation links work across components; isolated logs alone cannot reconstruct spans reliably.
- Cache-key design determines which requests may share cached content.
- Correlation IDs allow developers to join related log records and reduce noisy searches.
Explanation
Correct Answer
C:Cache-key design determines which requests may share cached content. This is the governing behavior behind the recommended change: configure cache keys or origin request policies using the required safe variation dimensions.
Incorrect Answers
A:The statement describes concurrency backpressure, which is not the controlling AWS behavior for this API response caching variation situation. The required implementation is: configure cache keys or origin request policies using the required safe variation dimensions.
B:The statement describes X-Ray trace propagation, which is not the controlling AWS behavior for this API response caching variation situation. The required implementation is: configure cache keys or origin request policies using the required safe variation dimensions.
D:The statement describes CloudWatch Logs Insights root cause, which is not the controlling AWS behavior for this API response caching variation situation. The required implementation is: configure cache keys or origin request policies using the required safe variation dimensions.
Question 359
A deployment artifact should use the same IaC source but separate S3 bucket names by environment. A teammate asks why the proposed CloudFormation resource parameters approach is technically appropriate. Which AWS behavior BEST explains the decision?
- Event-driven tests must exercise the actual source envelope and partial failure contract.
- API Gateway stage configuration can parameterize integrations for separate environments.
- Template parameters and mappings allow controlled environment variation from one IaC definition.
- CPU architecture and container-image manifests must match the target runtime.
Explanation
Correct Answer
C:Template parameters and mappings allow controlled environment variation from one IaC definition. This is the governing behavior behind the recommended change: parameterize the CloudFormation or SAM template and supply environment-specific values at deployment.
Incorrect Answers
A:The statement describes SQS handler contract tests, which is not the controlling AWS behavior for this CloudFormation resource parameters situation. The required implementation is: parameterize the CloudFormation or SAM template and supply environment-specific values at deployment.
B:The statement describes API Gateway stage variables, which is not the controlling AWS behavior for this CloudFormation resource parameters situation. The required implementation is: parameterize the CloudFormation or SAM template and supply environment-specific values at deployment.
D:The statement describes container image architecture compatibility, which is not the controlling AWS behavior for this CloudFormation resource parameters situation. The required implementation is: parameterize the CloudFormation or SAM template and supply environment-specific values at deployment.
Question 360
A locally run test harness needs role credentials to call a single AWS API without storing secrets in its repository. A teammate asks why the proposed temporary credential storage approach is technically appropriate. Which AWS behavior BEST explains the decision?
- JWT verification checks cryptographic signature and claims, not only whether a header exists.
- Encryption at rest does not stop an application from leaking plaintext secrets during logging.
- AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets.
- Resource policies can restrict the source principals or network context independently from route authorizers.
Explanation
Correct Answer
C:AWS credential provider chains support ephemeral sessions and remove the need for embedded static secrets. This is the governing behavior behind the recommended change: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
Incorrect Answers
A:The statement describes API Gateway JWT authorizer, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
B:The statement describes Lambda environment secret leakage, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.
D:The statement describes API Gateway resource policy, which is not the controlling AWS behavior for this temporary credential storage situation. The required implementation is: use the AWS SDK default credential chain with short-lived credentials from an approved profile or federation.