Question 310

At a SaaS procurement platform, engineers need to lower generation expense for repeated identical approved requests. The migration must preserve existing downstream API contracts. An architecture review has rejected fixes that only conceal the symptoms. Which remediation addresses the root problem?

  1. Increase output tokens for repeated requests
  2. Cache eligible responses using policy-aware keys and expiry rules
  3. Invoke the full model every time regardless of repeat rate
  4. Disable authorization checks when a response is served from cache

Explanation

Correct Answer

B:

Response caching avoids repeated inference when inputs and authorization context permit reuse. In a SaaS procurement platform, the engineering team should verify this design against its stated objective to lower generation expense for repeated identical approved requests, including the requirement that the migration must preserve existing downstream API contracts.

Incorrect Answers

A:

The suggested action—increase output tokens for repeated requests—does not establish the required control for a SaaS procurement platform to lower generation expense for repeated identical approved requests. It replaces a verifiable engineering control with an untested shortcut in the a SaaS procurement platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—invoke the full model every time regardless of repeat rate—does not establish the required control for a SaaS procurement platform to lower generation expense for repeated identical approved requests. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a SaaS procurement platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—disable authorization checks when a response is served from cache—does not establish the required control for a SaaS procurement platform to lower generation expense for repeated identical approved requests. It replaces a verifiable engineering control with an untested shortcut in the a SaaS procurement platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 311

At a shipping brokerage, engineers need to diagnose slow approximate nearest-neighbor retrieval at peak scale. The deployment has both bursty and sustained workloads. The team wants a solution that can be validated through targeted test cases. What should the lead engineer recommend?

  1. Assume a single lookup proves sustained throughput
  2. Profile vector-query latency, index settings and metadata filters
  3. Increase generation output limits to fix database latency
  4. Rebuild the prompt template without checking search timings

Explanation

Correct Answer

B:

Retrieval performance needs index-level measurement rather than inference-only tuning. In a shipping brokerage, the engineering team should verify this design against its stated objective to diagnose slow approximate nearest-neighbor retrieval at peak scale, including the requirement that the deployment has both bursty and sustained workloads.

Incorrect Answers

A:

The suggested action—assume a single lookup proves sustained throughput—does not establish the required control for a shipping brokerage to diagnose slow approximate nearest-neighbor retrieval at peak scale. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a shipping brokerage. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—increase generation output limits to fix database latency—does not establish the required control for a shipping brokerage to diagnose slow approximate nearest-neighbor retrieval at peak scale. The change is applied outside the component responsible for the requirement identified by a shipping brokerage. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—rebuild the prompt template without checking search timings—does not establish the required control for a shipping brokerage to diagnose slow approximate nearest-neighbor retrieval at peak scale. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a shipping brokerage. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 312

At a wholesale distribution platform, engineers need to reduce end-to-end latency of independent retrieval and policy checks. The deployment has both bursty and sustained workloads. The team wants a solution that can be validated through targeted test cases. Which remediation addresses the root problem?

  1. Serialize every independent request by default
  2. Remove validation to conceal latency
  3. Assume shorter prompts always compensate for network bottlenecks
  4. Execute safe independent stages concurrently and join their results before generation

Explanation

Correct Answer

D:

Parallel work can reduce critical-path latency when stages have no dependency. In a wholesale distribution platform, the engineering team should verify this design against its stated objective to reduce end-to-end latency of independent retrieval and policy checks, including the requirement that the deployment has both bursty and sustained workloads.

Incorrect Answers

A:

The suggested action—serialize every independent request by default—does not establish the required control for a wholesale distribution platform to reduce end-to-end latency of independent retrieval and policy checks. It replaces a verifiable engineering control with an untested shortcut in the a wholesale distribution platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—remove validation to conceal latency—does not establish the required control for a wholesale distribution platform to reduce end-to-end latency of independent retrieval and policy checks. The change is applied outside the component responsible for the requirement identified by a wholesale distribution platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—assume shorter prompts always compensate for network bottlenecks—does not establish the required control for a wholesale distribution platform to reduce end-to-end latency of independent retrieval and policy checks. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a wholesale distribution platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 313

At a commercial property platform, engineers need to detect and redact personal identifiers before sending user documents to inference. Response reliability is more important than free-form creativity. An architecture review has rejected fixes that only conceal the symptoms. Which implementation most directly satisfies the requirement?

  1. Use an S3 bucket name as a data redaction control
  2. Log entire unmasked prompts to every debugging dashboard
  3. Classify PII and apply approved redaction or masking before invocation
  4. Send raw identifiers and ask the model to forget them afterward

Explanation

Correct Answer

C:

Data minimization reduces exposure before sensitive information enters the model interaction. In a commercial property platform, the engineering team should verify this design against its stated objective to detect and redact personal identifiers before sending user documents to inference, including the requirement that response reliability is more important than free-form creativity.

Incorrect Answers

A:

The suggested action—use an S3 bucket name as a data redaction control—does not establish the required control for a commercial property platform to detect and redact personal identifiers before sending user documents to inference. It replaces a verifiable engineering control with an untested shortcut in the a commercial property platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—log entire unmasked prompts to every debugging dashboard—does not establish the required control for a commercial property platform to detect and redact personal identifiers before sending user documents to inference. The change is applied outside the component responsible for the requirement identified by a commercial property platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—send raw identifiers and ask the model to forget them afterward—does not establish the required control for a commercial property platform to detect and redact personal identifiers before sending user documents to inference. It replaces a verifiable engineering control with an untested shortcut in the a commercial property platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 314

At a travel services company, engineers need to resolve truncated answers when prompts exceed model context limits. The architecture must minimize avoidable data exposure. An architecture review has rejected fixes that only conceal the symptoms. Which design decision addresses the underlying issue?

  1. Inspect token budgets and adapt history, retrieval context and output allowances
  2. Raise temperature to make the context window larger
  3. Remove HTTP retry logic to increase model memory
  4. Change IAM credentials to expand a token limit

Explanation

Correct Answer

A:

Context-window errors require input and output token budgeting, not authorization changes. In a travel services company, the engineering team should verify this design against its stated objective to resolve truncated answers when prompts exceed model context limits, including the requirement that the architecture must minimize avoidable data exposure.

Incorrect Answers

B:

The suggested action—raise temperature to make the context window larger—does not establish the required control for a travel services company to resolve truncated answers when prompts exceed model context limits. It replaces a verifiable engineering control with an untested shortcut in the a travel services company deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—remove HTTP retry logic to increase model memory—does not establish the required control for a travel services company to resolve truncated answers when prompts exceed model context limits. The change is applied outside the component responsible for the requirement identified by a travel services company. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—change IAM credentials to expand a token limit—does not establish the required control for a travel services company to resolve truncated answers when prompts exceed model context limits. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a travel services company. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 315

At a pharmaceutical documentation team, engineers need to keep FM invocation access off public internet paths where supported. The solution must tolerate transient dependency failures. An architecture review has rejected fixes that only conceal the symptoms. Which architecture is best supported by the stated constraints?

  1. Assume TLS encryption alone makes every path private
  2. Expose internal endpoints publicly without authentication
  3. Embed root account keys in model prompts
  4. Use supported VPC interface endpoints and restrictive IAM/network controls

Explanation

Correct Answer

D:

Private connectivity and identity restrictions address separate network and authorization concerns. In a pharmaceutical documentation team, the engineering team should verify this design against its stated objective to keep FM invocation access off public internet paths where supported, including the requirement that the solution must tolerate transient dependency failures.

Incorrect Answers

A:

The suggested action—assume TLS encryption alone makes every path private—does not establish the required control for a pharmaceutical documentation team to keep FM invocation access off public internet paths where supported. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a pharmaceutical documentation team. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—expose internal endpoints publicly without authentication—does not establish the required control for a pharmaceutical documentation team to keep FM invocation access off public internet paths where supported. It replaces a verifiable engineering control with an untested shortcut in the a pharmaceutical documentation team deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—embed root account keys in model prompts—does not establish the required control for a pharmaceutical documentation team to keep FM invocation access off public internet paths where supported. The change is applied outside the component responsible for the requirement identified by a pharmaceutical documentation team. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 316

At a nonprofit grant portal, engineers need to combine content filters with custom domain-specific safety policy. The current deployment processes customer-specific information. The team wants a solution that can be validated through targeted test cases. Which design decision addresses the underlying issue?

  1. Disable tool authorization after adding content filtering
  2. Accept all outputs that pass JSON parsing regardless of policy
  3. Layer model guardrails with application validation and post-processing checks
  4. Assume one generic keyword list covers every threat class

Explanation

Correct Answer

C:

Defense in depth covers different failure modes at independent enforcement points. In a nonprofit grant portal, the engineering team should verify this design against its stated objective to combine content filters with custom domain-specific safety policy, including the requirement that the current deployment processes customer-specific information.

Incorrect Answers

A:

The suggested action—disable tool authorization after adding content filtering—does not establish the required control for a nonprofit grant portal to combine content filters with custom domain-specific safety policy. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a nonprofit grant portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—accept all outputs that pass JSON parsing regardless of policy—does not establish the required control for a nonprofit grant portal to combine content filters with custom domain-specific safety policy. It replaces a verifiable engineering control with an untested shortcut in the a nonprofit grant portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—assume one generic keyword list covers every threat class—does not establish the required control for a nonprofit grant portal to combine content filters with custom domain-specific safety policy. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a nonprofit grant portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 317

At a nonprofit grant portal, engineers need to spot unexpected cost spikes caused by unusually long generated responses. The change must be auditable and reversible. The team wants a solution that can be validated through targeted test cases. What should be implemented before scaling this workflow?

  1. Inspect the most recent prompt manually once per quarter
  2. Assume a stable request count guarantees stable token consumption
  3. Collect token usage and cost metrics per workflow with anomaly alerts
  4. Monitor HTTP success codes only

Explanation

Correct Answer

C:

Token-level measurements reveal costs hidden by request-count dashboards. In a nonprofit grant portal, the engineering team should verify this design against its stated objective to spot unexpected cost spikes caused by unusually long generated responses, including the requirement that the change must be auditable and reversible.

Incorrect Answers

A:

The suggested action—inspect the most recent prompt manually once per quarter—does not establish the required control for a nonprofit grant portal to spot unexpected cost spikes caused by unusually long generated responses. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a nonprofit grant portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—assume a stable request count guarantees stable token consumption—does not establish the required control for a nonprofit grant portal to spot unexpected cost spikes caused by unusually long generated responses. It replaces a verifiable engineering control with an untested shortcut in the a nonprofit grant portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—monitor HTTP success codes only—does not establish the required control for a nonprofit grant portal to spot unexpected cost spikes caused by unusually long generated responses. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a nonprofit grant portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 318

At a SaaS procurement platform, engineers need to validate a risky new model version before sending all production traffic. Monitoring should isolate failures to the responsible component. The team wants a solution that can be validated through targeted test cases. Which remediation addresses the root problem?

  1. Replace every production route at once without evaluation
  2. Assume offline model benchmarks guarantee production behavior
  3. Disable monitoring until the new model stabilizes
  4. Deploy a measured canary with rollback thresholds and human review as required

Explanation

Correct Answer

D:

Canary evaluation detects live regressions under limited exposure. In a SaaS procurement platform, the engineering team should verify this design against its stated objective to validate a risky new model version before sending all production traffic, including the requirement that monitoring should isolate failures to the responsible component.

Incorrect Answers

A:

The suggested action—replace every production route at once without evaluation—does not establish the required control for a SaaS procurement platform to validate a risky new model version before sending all production traffic. It replaces a verifiable engineering control with an untested shortcut in the a SaaS procurement platform deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

B:

The suggested action—assume offline model benchmarks guarantee production behavior—does not establish the required control for a SaaS procurement platform to validate a risky new model version before sending all production traffic. The change is applied outside the component responsible for the requirement identified by a SaaS procurement platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—disable monitoring until the new model stabilizes—does not establish the required control for a SaaS procurement platform to validate a risky new model version before sending all production traffic. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a SaaS procurement platform. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 319

At a global manufacturer, engineers need to switch model providers without modifying application business logic. Monitoring should isolate failures to the responsible component. The initial assessment isolates this issue from unrelated infrastructure changes. Which implementation most directly satisfies the requirement?

  1. Introduce a model adapter and externalized routing configuration
  2. Embed provider-specific request formats in every user interface
  3. Hard-code one model ID in all business services
  4. Depend on prompt wording to silently change cloud providers

Explanation

Correct Answer

A:

An abstraction layer isolates provider requests and lets configuration drive changes. In a global manufacturer, the engineering team should verify this design against its stated objective to switch model providers without modifying application business logic, including the requirement that monitoring should isolate failures to the responsible component.

Incorrect Answers

B:

The suggested action—embed provider-specific request formats in every user interface—does not establish the required control for a global manufacturer to switch model providers without modifying application business logic. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a global manufacturer. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—hard-code one model ID in all business services—does not establish the required control for a global manufacturer to switch model providers without modifying application business logic. It replaces a verifiable engineering control with an untested shortcut in the a global manufacturer deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—depend on prompt wording to silently change cloud providers—does not establish the required control for a global manufacturer to switch model providers without modifying application business logic. The change is applied outside the component responsible for the requirement identified by a global manufacturer. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

Question 320

At a legal case-management provider, engineers need to keep FM invocation access off public internet paths where supported. The current deployment processes customer-specific information. The team wants a solution that can be validated through targeted test cases. Which change should the team prioritize?

  1. Use supported VPC interface endpoints and restrictive IAM/network controls
  2. Assume TLS encryption alone makes every path private
  3. Expose internal endpoints publicly without authentication
  4. Embed root account keys in model prompts

Explanation

Correct Answer

A:

Private connectivity and identity restrictions address separate network and authorization concerns. In a legal case-management provider, the engineering team should verify this design against its stated objective to keep FM invocation access off public internet paths where supported, including the requirement that the current deployment processes customer-specific information.

Incorrect Answers

B:

The suggested action—assume TLS encryption alone makes every path private—does not establish the required control for a legal case-management provider to keep FM invocation access off public internet paths where supported. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a legal case-management provider. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

C:

The suggested action—expose internal endpoints publicly without authentication—does not establish the required control for a legal case-management provider to keep FM invocation access off public internet paths where supported. It replaces a verifiable engineering control with an untested shortcut in the a legal case-management provider deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

D:

The suggested action—embed root account keys in model prompts—does not establish the required control for a legal case-management provider to keep FM invocation access off public internet paths where supported. The change is applied outside the component responsible for the requirement identified by a legal case-management provider. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.

AWS Certified Generative AI Developer - Professional AIP-C01 Practice Tests