Amazon AWS Certified Developer - Associate DVA-C02 Practice Test 46
Question 450
A search box must find phrases and relevance-ranked matches across an indexed document corpus. Suppose the team omits the intended OpenSearch full-text queries safeguard. Which failure mode is the MOST direct risk of that omission?
- A DynamoDB key-only Query cannot perform arbitrary relevance-ranked text search.
- Using Scan for a predictable partition lookup wastes read capacity and creates latency.
- A too-short visibility timeout lets another consumer receive unfinished work.
- The execution role lacks a required resource permission and AWS denies the API call.
Explanation
Correct Answer
A:A DynamoDB key-only Query cannot perform arbitrary relevance-ranked text search. The planned prevention is to index searchable fields in Amazon OpenSearch Service and query the text index with an appropriate analyzer; the most direct verification is that search results return ranked text matches according to indexed tokens and query clauses.
Incorrect Answers
B:That failure mechanism is associated with DynamoDB Query versus Scan. The omitted OpenSearch full-text queries protection instead causes this problem: a DynamoDB key-only Query cannot perform arbitrary relevance-ranked text search.
C:That failure mechanism is associated with SQS visibility timeout. The omitted OpenSearch full-text queries protection instead causes this problem: a DynamoDB key-only Query cannot perform arbitrary relevance-ranked text search.
D:That failure mechanism is associated with Lambda execution role least privilege. The omitted OpenSearch full-text queries protection instead causes this problem: a DynamoDB key-only Query cannot perform arbitrary relevance-ranked text search.
Question 451
A shared AWS account has several Lambda functions and one bursty worker should not exhaust all available concurrency. Suppose the team omits the intended Lambda concurrency reservation safeguard. Which failure mode is the MOST direct risk of that omission?
- Uncontrolled shared concurrency can let a noisy function starve other executions.
- Treating an async DLQ as a complete execution trace omits response context.
- Querying a nonkey base attribute without an index forces a scan or invalid key expression.
- Without redrive, poison messages are repeatedly delivered and hide useful errors.
Explanation
Correct Answer
A:Uncontrolled shared concurrency can let a noisy function starve other executions. The planned prevention is to configure reserved concurrency for the critical function at a measured level within account limits; the most direct verification is that function concurrency metrics show the reserved limit applied and other functions retain available capacity.
Incorrect Answers
B:That failure mechanism is associated with Lambda destinations versus DLQ. The omitted Lambda concurrency reservation protection instead causes this problem: uncontrolled shared concurrency can let a noisy function starve other executions.
C:That failure mechanism is associated with DynamoDB GSI access pattern. The omitted Lambda concurrency reservation protection instead causes this problem: uncontrolled shared concurrency can let a noisy function starve other executions.
D:That failure mechanism is associated with SQS dead-letter queues. The omitted Lambda concurrency reservation protection instead causes this problem: uncontrolled shared concurrency can let a noisy function starve other executions.
Question 452
A successful signup must independently notify billing, analytics, and email workers without sequential calls. Suppose the team omits the intended SNS fanout delivery safeguard. Which failure mode is the MOST direct risk of that omission?
- Invoking each downstream worker synchronously couples availability and latency.
- Never expiring cached entries can continue to return stale records after updates.
- Missing security-group or routing rules prevent TCP access to a private endpoint.
- Immediate unbounded retries amplify throttling and can repeat non-idempotent operations.
Explanation
Correct Answer
A:Invoking each downstream worker synchronously couples availability and latency. The planned prevention is to publish the event to SNS and subscribe separate SQS queues for each independently processed concern; the most direct verification is that each subscriber queue receives its own copy and an unavailable worker can process its backlog later.
Incorrect Answers
B:That failure mechanism is associated with ElastiCache cache-aside. The omitted SNS fanout delivery protection instead causes this problem: invoking each downstream worker synchronously couples availability and latency.
C:That failure mechanism is associated with Lambda VPC private data access. The omitted SNS fanout delivery protection instead causes this problem: invoking each downstream worker synchronously couples availability and latency.
D:That failure mechanism is associated with SDK adaptive retries. The omitted SNS fanout delivery protection instead causes this problem: invoking each downstream worker synchronously couples availability and latency.
Question 453
A table stores millions of tenant messages but most writes share one constant partition key. Suppose the team omits the intended DynamoDB partition key cardinality safeguard. Which failure mode is the MOST direct risk of that omission?
- Accepting generated code without review can introduce incorrect APIs or excessive permissions.
- An unconditional PutItem can overwrite valid concurrent state without a conflict signal.
- Missing security-group or routing rules prevent TCP access to a private endpoint.
- A low-cardinality or hot partition key concentrates traffic despite available table capacity.
Explanation
Correct Answer
D:A low-cardinality or hot partition key concentrates traffic despite available table capacity. The planned prevention is to choose a high-cardinality partition-key design that spreads requests while preserving required access patterns; the most direct verification is that consumed capacity and throttling metrics distribute more evenly across partition keys.
Incorrect Answers
A:That failure mechanism is associated with Amazon Q Developer review. The omitted DynamoDB partition key cardinality protection instead causes this problem: a low-cardinality or hot partition key concentrates traffic despite available table capacity.
B:That failure mechanism is associated with DynamoDB conditional update. The omitted DynamoDB partition key cardinality protection instead causes this problem: a low-cardinality or hot partition key concentrates traffic despite available table capacity.
C:That failure mechanism is associated with Lambda VPC private data access. The omitted DynamoDB partition key cardinality protection instead causes this problem: a low-cardinality or hot partition key concentrates traffic despite available table capacity.
Question 454
A serverless handler loads a vendor token but currently prints all environment variables on errors. Suppose the team omits the intended Lambda environment secret leakage safeguard. Which failure mode is the MOST direct risk of that omission?
- Omitting the source restriction can leave a supposedly internal API exposed to more callers.
- Removing a secret from the latest file does not erase its exposure in repository history.
- Dumping secrets into CloudWatch Logs exposes credentials to log readers.
- Adding another Allow statement does not override an explicit Deny.
Explanation
Correct Answer
C:Dumping secrets into CloudWatch Logs exposes credentials to log readers. The planned prevention is to redact secret-bearing environment values and authorization headers from structured application logs; the most direct verification is that controlled failure tests produce usable trace metadata but no credential material in logs.
Incorrect Answers
A:That failure mechanism is associated with API Gateway resource policy. The omitted Lambda environment secret leakage protection instead causes this problem: dumping secrets into CloudWatch Logs exposes credentials to log readers.
B:That failure mechanism is associated with secret scanning in CI. The omitted Lambda environment secret leakage protection instead causes this problem: dumping secrets into CloudWatch Logs exposes credentials to log readers.
D:That failure mechanism is associated with IAM policy explicit deny. The omitted Lambda environment secret leakage protection instead causes this problem: dumping secrets into CloudWatch Logs exposes credentials to log readers.
Question 455
A Lambda function update must route only 10 percent of traffic to a new version before full rollout. Suppose the team omits the intended CodeDeploy Lambda canary safeguard. Which failure mode is the MOST direct risk of that omission?
- A pipeline that rebuilds a different artifact after approval breaks artifact provenance.
- An AI test that only checks process exit can pass while functional behavior is wrong.
- Switching all traffic at once removes early canary detection.
- Insufficient /tmp space causes disk write failures regardless of the function's available heap.
Explanation
Correct Answer
C:Switching all traffic at once removes early canary detection. The planned prevention is to configure CodeDeploy Lambda traffic shifting with alarms and a tested rollback policy; the most direct verification is that alias routing starts at the selected small percentage and alarms can trigger rollback.
Incorrect Answers
A:That failure mechanism is associated with CodePipeline gated promotion. The omitted CodeDeploy Lambda canary protection instead causes this problem: switching all traffic at once removes early canary detection.
B:That failure mechanism is associated with AI-assisted test review. The omitted CodeDeploy Lambda canary protection instead causes this problem: switching all traffic at once removes early canary detection.
D:That failure mechanism is associated with Lambda ephemeral disk sizing. The omitted CodeDeploy Lambda canary protection instead causes this problem: switching all traffic at once removes early canary detection.
Question 456
An application role in account B must decrypt objects encrypted under a customer-managed KMS key in account A. Suppose the team omits the intended KMS key-policy cross-account safeguard. Which failure mode is the MOST direct risk of that omission?
- An S3 object permission alone does not give decrypt access to its KMS key.
- A role allowed to GetObject but denied KMS Decrypt cannot read the plaintext.
- Logging or returning raw records before masking exposes PII despite correct database encryption.
- Adding another Allow statement does not override an explicit Deny.
Explanation
Correct Answer
A:The planned prevention is to authorize the external principal through the KMS key policy and the caller's IAM permissions for the needed cryptographic operation; the most direct verification is that the external role can use the approved KMS key while unrelated principals remain denied.
Incorrect Answers
B:That failure mechanism is associated with S3 SSE-KMS access. The omitted KMS key-policy cross-account protection instead causes this problem: an S3 object permission alone does not give decrypt access to its KMS key.
C:That failure mechanism is associated with PII response field masking. The omitted KMS key-policy cross-account protection instead causes this problem: an S3 object permission alone does not give decrypt access to its KMS key.
D:That failure mechanism is associated with IAM policy explicit deny. The omitted KMS key-policy cross-account protection instead causes this problem: an S3 object permission alone does not give decrypt access to its KMS key.
Question 457
An API should be callable only from a known VPC endpoint, not the entire internet. Suppose the team omits the intended API Gateway resource policy safeguard. Which failure mode is the MOST direct risk of that omission?
- Omitting the source restriction can leave a supposedly internal API exposed to more callers.
- Accepting a caller-supplied tenant key without validation enables cross-tenant record access.
- A long-lived credential hardcoded into a container image stays stale after rotation.
- Confusing a user pool with an identity pool leaves the app without the expected login and user-directory flow.
Explanation
Correct Answer
A:Omitting the source restriction can leave a supposedly internal API exposed to more callers. The planned prevention is to define an API Gateway resource policy with explicit conditions for approved source VPC endpoints; the most direct verification is that requests from the intended endpoint succeed and other source contexts receive access denied.
Incorrect Answers
B:That failure mechanism is associated with multi-tenant DynamoDB row isolation. The omitted API Gateway resource policy protection instead causes this problem: omitting the source restriction can leave a supposedly internal API exposed to more callers.
C:That failure mechanism is associated with Secrets Manager rotation. The omitted API Gateway resource policy protection instead causes this problem: omitting the source restriction can leave a supposedly internal API exposed to more callers.
D:That failure mechanism is associated with Cognito user pool authentication. The omitted API Gateway resource policy protection instead causes this problem: omitting the source restriction can leave a supposedly internal API exposed to more callers.
Question 458
A team uses Amazon Q Developer to propose a test suite for a refactored Python handler. Suppose the team omits the intended AI-assisted test review safeguard. Which failure mode is the MOST direct risk of that omission?
- A mutable latest tag can point to different image bytes on separate deployments.
- Manual configuration changes may be overwritten or missed by the next IaC deployment.
- A hardcoded backend alias in a shared integration can route test traffic into production.
- An AI test that only checks process exit can pass while functional behavior is wrong.
Explanation
Correct Answer
D:The planned prevention is to review AI-generated tests for assertions, data privacy, and realistic events before adding them to CI; the most direct verification is that the accepted tests fail on a known bug and pass once the defect is fixed without leaking secrets.
Incorrect Answers
A:That failure mechanism is associated with immutable container image tags. The omitted AI-assisted test review protection instead causes this problem: an AI test that only checks process exit can pass while functional behavior is wrong.
B:That failure mechanism is associated with infrastructure drift detection. The omitted AI-assisted test review protection instead causes this problem: an AI test that only checks process exit can pass while functional behavior is wrong.
C:That failure mechanism is associated with API Gateway stage variables. The omitted AI-assisted test review protection instead causes this problem: an AI test that only checks process exit can pass while functional behavior is wrong.
Question 459
A single infrastructure template must deploy a dev and prod stack with different memory settings. Suppose the team omits the intended CloudFormation resource parameters safeguard. Which failure mode is the MOST direct risk of that omission?
- Replacing all tasks in place can increase downtime or remove a quick rollback path.
- A malformed template can fail deployment even if application unit tests pass.
- Insufficient /tmp space causes disk write failures regardless of the function's available heap.
- Hardcoding production resource names in a shared template can cause cross-environment collisions.
Explanation
Correct Answer
D:Hardcoding production resource names in a shared template can cause cross-environment collisions. The planned prevention is to parameterize the CloudFormation or SAM template and supply environment-specific values at deployment; the most direct verification is that the change set shows the intended resource values for the selected environment without modifying source templates.
Incorrect Answers
A:That failure mechanism is associated with CodeDeploy ECS blue-green. The omitted CloudFormation resource parameters protection instead causes this problem: hardcoding production resource names in a shared template can cause cross-environment collisions.
B:That failure mechanism is associated with SAM template validation. The omitted CloudFormation resource parameters protection instead causes this problem: hardcoding production resource names in a shared template can cause cross-environment collisions.
C:That failure mechanism is associated with Lambda ephemeral disk sizing. The omitted CloudFormation resource parameters protection instead causes this problem: hardcoding production resource names in a shared template can cause cross-environment collisions.
Question 460
An onboarding workflow invokes verification, account creation, and compensation with observable retries. Suppose the team omits the intended Step Functions orchestration safeguard. Which failure mode is the MOST direct risk of that omission?
- A producer hardcoded to one downstream endpoint cannot independently route new event types.
- Missing or incorrect event filter patterns cause unwanted work or dropped eligible records.
- A missing destination silently loses terminal failure context beyond default handling.
- A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
Explanation
Correct Answer
D:A one-shot Lambda chain obscures per-step recovery and can exceed execution constraints. The planned prevention is to use AWS Step Functions to coordinate states, retries, catches, and compensating tasks explicitly; the most direct verification is that execution history shows state transitions, retries, and the branch taken after an error.
Incorrect Answers
A:That failure mechanism is associated with EventBridge event routing. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
B:That failure mechanism is associated with Lambda event filtering. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.
C:That failure mechanism is associated with Lambda asynchronous failure destination. The omitted Step Functions orchestration protection instead causes this problem: a one-shot Lambda chain obscures per-step recovery and can exceed execution constraints.