Question 190
At a public-sector document office, engineers need to explain new API invocation failures following an integration change. Monitoring should isolate failures to the responsible component. The team wants a solution that can be validated through targeted test cases. Which architecture is best supported by the stated constraints?
- Assume all 4xx and 5xx errors have the same root cause
- Inspect status codes, SDK errors, model access permissions and request shapes
- Reduce the retriever top-k without examining the failed request
- Increase model randomness to fix IAM denial
Explanation
Correct Answer
B:Integration debugging differentiates authorization, validation, throttling and service failures. In a public-sector document office, the engineering team should verify this design against its stated objective to explain new API invocation failures following an integration change, including the requirement that monitoring should isolate failures to the responsible component.
Incorrect Answers
A:The suggested action—assume all 4xx and 5xx errors have the same root cause—does not establish the required control for a public-sector document office to explain new API invocation failures following an integration change. It replaces a verifiable engineering control with an untested shortcut in the a public-sector document office deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—reduce the retriever top-k without examining the failed request—does not establish the required control for a public-sector document office to explain new API invocation failures following an integration change. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a public-sector document office. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—increase model randomness to fix IAM denial—does not establish the required control for a public-sector document office to explain new API invocation failures following an integration change. It replaces a verifiable engineering control with an untested shortcut in the a public-sector document office deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 191
At a security incident response team, engineers need to deploy a large self-hosted model with significant GPU memory needs. The architecture must avoid unnecessary coupling between components. A recent review found that the current design has no reliable safeguard for this case. Which implementation most directly satisfies the requirement?
- Assume endpoint throughput is independent of generated token length
- Run a large GPU workload in an API Gateway mapping template
- Size accelerator memory, batching, concurrency and model-loading strategy explicitly
- Treat model deployment as a CPU-only static web hosting task
Explanation
Correct Answer
C:Self-hosted LLM serving must account for memory, accelerator use and token generation dynamics. In a security incident response team, the engineering team should verify this design against its stated objective to deploy a large self-hosted model with significant GPU memory needs, including the requirement that the architecture must avoid unnecessary coupling between components.
Incorrect Answers
A:The suggested action—assume endpoint throughput is independent of generated token length—does not establish the required control for a security incident response team to deploy a large self-hosted model with significant GPU memory needs. It replaces a verifiable engineering control with an untested shortcut in the a security incident response team deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—run a large GPU workload in an API Gateway mapping template—does not establish the required control for a security incident response team to deploy a large self-hosted model with significant GPU memory needs. The change is applied outside the component responsible for the requirement identified by a security incident response team. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—treat model deployment as a CPU-only static web hosting task—does not establish the required control for a security incident response team to deploy a large self-hosted model with significant GPU memory needs. It replaces a verifiable engineering control with an untested shortcut in the a security incident response team deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 192
At a university research portal, engineers need to keep an entire policy section together across chunk boundaries. Operators need measurable acceptance criteria before rollout. The team wants a solution that can be validated through targeted test cases. Which remediation addresses the root problem?
- Split every document into single-character chunks
- Use randomly sized chunks without overlap or structure
- Increase model output tokens without improving context selection
- Use structure-aware or hierarchical chunking and test answer recall
Explanation
Correct Answer
D:Structure-sensitive chunking preserves relationships between headings and text. In a university research portal, the engineering team should verify this design against its stated objective to keep an entire policy section together across chunk boundaries, including the requirement that operators need measurable acceptance criteria before rollout.
Incorrect Answers
A:The suggested action—split every document into single-character chunks—does not establish the required control for a university research portal to keep an entire policy section together across chunk boundaries. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a university research portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—use randomly sized chunks without overlap or structure—does not establish the required control for a university research portal to keep an entire policy section together across chunk boundaries. It replaces a verifiable engineering control with an untested shortcut in the a university research portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—increase model output tokens without improving context selection—does not establish the required control for a university research portal to keep an entire policy section together across chunk boundaries. The change is applied outside the component responsible for the requirement identified by a university research portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 193
At a university research portal, engineers need to publish an internal GenAI service with an explicit, testable API schema. A controlled rollout is required before broad user exposure. An architecture review has rejected fixes that only conceal the symptoms. Which remediation addresses the root problem?
- Use the vector dimension as the API version
- Define an OpenAPI contract with request validation and stable versions
- Describe the API exclusively in unversioned prompt instructions
- Let consumers guess request parameters from generated examples
Explanation
Correct Answer
B:API-first contracts reduce ambiguous integration and support compatibility testing. In a university research portal, the engineering team should verify this design against its stated objective to publish an internal GenAI service with an explicit, testable API schema, including the requirement that a controlled rollout is required before broad user exposure.
Incorrect Answers
A:The suggested action—use the vector dimension as the API version—does not establish the required control for a university research portal to publish an internal GenAI service with an explicit, testable API schema. It replaces a verifiable engineering control with an untested shortcut in the a university research portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—describe the API exclusively in unversioned prompt instructions—does not establish the required control for a university research portal to publish an internal GenAI service with an explicit, testable API schema. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a university research portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—let consumers guess request parameters from generated examples—does not establish the required control for a university research portal to publish an internal GenAI service with an explicit, testable API schema. It replaces a verifiable engineering control with an untested shortcut in the a university research portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 194
At an automotive parts supplier, engineers need to spot unexpected cost spikes caused by unusually long generated responses. The change must be auditable and reversible. A recent review found that the current design has no reliable safeguard for this case. Which architecture is best supported by the stated constraints?
- Monitor HTTP success codes only
- Inspect the most recent prompt manually once per quarter
- Assume a stable request count guarantees stable token consumption
- Collect token usage and cost metrics per workflow with anomaly alerts
Explanation
Correct Answer
D:Token-level measurements reveal costs hidden by request-count dashboards. In an automotive parts supplier, 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—monitor HTTP success codes only—does not establish the required control for an automotive parts supplier to spot unexpected cost spikes caused by unusually long generated responses. It replaces a verifiable engineering control with an untested shortcut in the an automotive parts supplier deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—inspect the most recent prompt manually once per quarter—does not establish the required control for an automotive parts supplier to spot unexpected cost spikes caused by unusually long generated responses. The change is applied outside the component responsible for the requirement identified by an automotive parts supplier. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—assume a stable request count guarantees stable token consumption—does not establish the required control for an automotive parts supplier 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 an automotive parts supplier. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 195
At a multilingual contact center, engineers need to change embedding models without corrupting nearest-neighbor comparisons. The implementation must remain maintainable across model upgrades. A recent review found that the current design has no reliable safeguard for this case. Which change should the team prioritize?
- Change only the vector database display name
- Increase the vector similarity threshold arbitrarily
- Re-embed the corpus and queries into the selected model's compatible vector space
- Compare new query vectors with old embeddings without validation
Explanation
Correct Answer
C:Embedding migrations require compatible representations and a controlled index cutover. In a multilingual contact center, the engineering team should verify this design against its stated objective to change embedding models without corrupting nearest-neighbor comparisons, including the requirement that the implementation must remain maintainable across model upgrades.
Incorrect Answers
A:The suggested action—change only the vector database display name—does not establish the required control for a multilingual contact center to change embedding models without corrupting nearest-neighbor comparisons. It replaces a verifiable engineering control with an untested shortcut in the a multilingual contact center deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—increase the vector similarity threshold arbitrarily—does not establish the required control for a multilingual contact center to change embedding models without corrupting nearest-neighbor comparisons. The change is applied outside the component responsible for the requirement identified by a multilingual contact center. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—compare new query vectors with old embeddings without validation—does not establish the required control for a multilingual contact center to change embedding models without corrupting nearest-neighbor comparisons. It replaces a verifiable engineering control with an untested shortcut in the a multilingual contact center deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 196
At a nonprofit grant portal, engineers need to provide inspectable evidence for a generated compliance recommendation. The current deployment processes customer-specific information. The initial assessment isolates this issue from unrelated infrastructure changes. Which design decision addresses the underlying issue?
- Hide uncertainty behind confident language
- Present internal unverified reasoning as an authoritative audit record
- Show relevant source citations and communicate uncertainty or limitations
- Invent citations to make the answer appear supported
Explanation
Correct Answer
C:Transparency is strengthened by grounded evidence and calibrated limitations. In a nonprofit grant portal, the engineering team should verify this design against its stated objective to provide inspectable evidence for a generated compliance recommendation, including the requirement that the current deployment processes customer-specific information.
Incorrect Answers
A:The suggested action—hide uncertainty behind confident language—does not establish the required control for a nonprofit grant portal to provide inspectable evidence for a generated compliance recommendation. The change is applied outside the component responsible for the requirement identified 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—present internal unverified reasoning as an authoritative audit record—does not establish the required control for a nonprofit grant portal to provide inspectable evidence for a generated compliance recommendation. 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.
D:The suggested action—invent citations to make the answer appear supported—does not establish the required control for a nonprofit grant portal to provide inspectable evidence for a generated compliance recommendation. The change is applied outside the component responsible for the requirement identified 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 197
At a pharmaceutical documentation team, engineers need to assess whether response quality differs materially across user groups. The solution must tolerate transient dependency failures. The initial assessment isolates this issue from unrelated infrastructure changes. What should the lead engineer recommend?
- Ignore differences whenever overall accuracy is high
- Run representative cohort evaluations using explicitly defined fairness metrics
- Evaluate a single demographic example and generalize to everyone
- Treat average latency as proof of unbiased outputs
Explanation
Correct Answer
B:Fairness requires subgroup-aware testing and responsible interpretation of metrics. In a pharmaceutical documentation team, the engineering team should verify this design against its stated objective to assess whether response quality differs materially across user groups, including the requirement that the solution must tolerate transient dependency failures.
Incorrect Answers
A:The suggested action—ignore differences whenever overall accuracy is high—does not establish the required control for a pharmaceutical documentation team to assess whether response quality differs materially across user groups. 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.
C:The suggested action—evaluate a single demographic example and generalize to everyone—does not establish the required control for a pharmaceutical documentation team to assess whether response quality differs materially across user groups. 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.
D:The suggested action—treat average latency as proof of unbiased outputs—does not establish the required control for a pharmaceutical documentation team to assess whether response quality differs materially across user groups. 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 198
At an automotive parts supplier, engineers need to improve vector search scale across independent business collections. Monitoring should isolate failures to the responsible component. A recent review found that the current design has no reliable safeguard for this case. What should the lead engineer recommend?
- Combine every document into a single giant chunk
- Increase generation temperature to speed vector queries
- Assume vector dimensionality alone determines throughput
- Partition or shard indexes according to query patterns and monitor recall and latency
Explanation
Correct Answer
D:Index layout and capacity decisions need workload-specific search performance measurements. In an automotive parts supplier, the engineering team should verify this design against its stated objective to improve vector search scale across independent business collections, including the requirement that monitoring should isolate failures to the responsible component.
Incorrect Answers
A:The suggested action—combine every document into a single giant chunk—does not establish the required control for an automotive parts supplier to improve vector search scale across independent business collections. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by an automotive parts supplier. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—increase generation temperature to speed vector queries—does not establish the required control for an automotive parts supplier to improve vector search scale across independent business collections. It replaces a verifiable engineering control with an untested shortcut in the an automotive parts supplier deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—assume vector dimensionality alone determines throughput—does not establish the required control for an automotive parts supplier to improve vector search scale across independent business collections. The change is applied outside the component responsible for the requirement identified by an automotive parts supplier. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 199
At a SaaS procurement platform, engineers need to obtain human approval before an agent executes a financial adjustment. A controlled rollout is required before broad user exposure. An architecture review has rejected fixes that only conceal the symptoms. Which remediation addresses the root problem?
- Store an unverified approval in the prompt
- Suspend the workflow for an explicit approval decision before the write action
- Let the model infer user consent from tone
- Complete the adjustment first and request approval later
Explanation
Correct Answer
B:Human-in-the-loop checkpoints should gate consequential actions before execution. In a SaaS procurement platform, the engineering team should verify this design against its stated objective to obtain human approval before an agent executes a financial adjustment, including the requirement that a controlled rollout is required before broad user exposure.
Incorrect Answers
A:The suggested action—store an unverified approval in the prompt—does not establish the required control for a SaaS procurement platform to obtain human approval before an agent executes a financial adjustment. 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.
C:The suggested action—let the model infer user consent from tone—does not establish the required control for a SaaS procurement platform to obtain human approval before an agent executes a financial adjustment. 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.
D:The suggested action—complete the adjustment first and request approval later—does not establish the required control for a SaaS procurement platform to obtain human approval before an agent executes a financial adjustment. 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 200
At a payment operations team, engineers need to validate a risky new model version before sending all production traffic. Monitoring should isolate failures to the responsible component. A recent review found that the current design has no reliable safeguard for this case. What should be implemented before scaling this workflow?
- Deploy a measured canary with rollback thresholds and human review as required
- Replace every production route at once without evaluation
- Assume offline model benchmarks guarantee production behavior
- Disable monitoring until the new model stabilizes
Explanation
Correct Answer
A:Canary evaluation detects live regressions under limited exposure. In a payment operations team, 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
B:The suggested action—replace every production route at once without evaluation—does not establish the required control for a payment operations team 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 payment operations team. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—assume offline model benchmarks guarantee production behavior—does not establish the required control for a payment operations team 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 payment operations team deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—disable monitoring until the new model stabilizes—does not establish the required control for a payment operations team 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 payment operations team. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.