Question 680
At an automotive parts supplier, engineers need to assess agent workflows that must call external tools accurately. Operators need measurable acceptance criteria before rollout. A recent review found that the current design has no reliable safeguard for this case. What should the lead engineer recommend?
- Count total tool calls and assume more is better
- Check only the model's prose fluency
- Ignore side effects and consider any final answer a success
- Measure task success, tool-choice correctness, authorization failures and excessive steps
Explanation
Correct Answer
D:Agent evaluation must include execution behavior and real task outcomes. In an automotive parts supplier, the engineering team should verify this design against its stated objective to assess agent workflows that must call external tools accurately, including the requirement that operators need measurable acceptance criteria before rollout.
Incorrect Answers
A:The suggested action—count total tool calls and assume more is better—does not establish the required control for an automotive parts supplier to assess agent workflows that must call external tools accurately. 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—check only the model's prose fluency—does not establish the required control for an automotive parts supplier to assess agent workflows that must call external tools accurately. 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—ignore side effects and consider any final answer a success—does not establish the required control for an automotive parts supplier to assess agent workflows that must call external tools accurately. 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 681
At an energy maintenance provider, engineers need to prepare model input that must satisfy a specific JSON request schema. Monitoring should isolate failures to the responsible component. A recent review found that the current design has no reliable safeguard for this case. Which architecture is best supported by the stated constraints?
- Pass free-form invalid JSON and rely on the service to repair it
- Mix response schemas from unrelated providers without conversion
- Use a larger context window to correct malformed fields
- Validate request structure and model-specific parameter types before invocation
Explanation
Correct Answer
D:Request validation prevents avoidable API failures and inconsistent model invocation. In an energy maintenance provider, the engineering team should verify this design against its stated objective to prepare model input that must satisfy a specific JSON request schema, including the requirement that monitoring should isolate failures to the responsible component.
Incorrect Answers
A:The suggested action—pass free-form invalid JSON and rely on the service to repair it—does not establish the required control for an energy maintenance provider to prepare model input that must satisfy a specific JSON request schema. The change is applied outside the component responsible for the requirement identified by an energy maintenance provider. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—mix response schemas from unrelated providers without conversion—does not establish the required control for an energy maintenance provider to prepare model input that must satisfy a specific JSON request schema. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by an energy maintenance provider. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—use a larger context window to correct malformed fields—does not establish the required control for an energy maintenance provider to prepare model input that must satisfy a specific JSON request schema. It replaces a verifiable engineering control with an untested shortcut in the an energy maintenance provider deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 682
At a legal case-management provider, engineers need to retrieve answers that require exact product codes and semantic similarity. The next release must be evaluated against the previous baseline. The initial assessment isolates this issue from unrelated infrastructure changes. Which change should the team prioritize?
- Combine keyword and vector retrieval with relevance evaluation
- Use only random document sampling
- Replace retrieval with a high-temperature model guess
- Remove product identifiers during preprocessing
Explanation
Correct Answer
A:Hybrid retrieval combines lexical matches with embedding-based semantic matches. In a legal case-management provider, the engineering team should verify this design against its stated objective to retrieve answers that require exact product codes and semantic similarity, including the requirement that the next release must be evaluated against the previous baseline.
Incorrect Answers
B:The suggested action—use only random document sampling—does not establish the required control for a legal case-management provider to retrieve answers that require exact product codes and semantic similarity. 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—replace retrieval with a high-temperature model guess—does not establish the required control for a legal case-management provider to retrieve answers that require exact product codes and semantic similarity. 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—remove product identifiers during preprocessing—does not establish the required control for a legal case-management provider to retrieve answers that require exact product codes and semantic similarity. 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.
Question 683
At a SaaS procurement platform, engineers need to limit prompt and response retention for a regulated application. Response reliability is more important than free-form creativity. An architecture review has rejected fixes that only conceal the symptoms. What is the most appropriate production approach?
- Write sensitive prompts to browser analytics automatically
- Set data retention and logging policies consistent with the compliance mandate
- Keep verbose unredacted invocation logs forever
- Assume disabling application logs eliminates all copies in supporting systems
Explanation
Correct Answer
B:Privacy controls must address the full data lifecycle, including diagnostic stores. In a SaaS procurement platform, the engineering team should verify this design against its stated objective to limit prompt and response retention for a regulated application, including the requirement that response reliability is more important than free-form creativity.
Incorrect Answers
A:The suggested action—write sensitive prompts to browser analytics automatically—does not establish the required control for a SaaS procurement platform to limit prompt and response retention for a regulated application. 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—keep verbose unredacted invocation logs forever—does not establish the required control for a SaaS procurement platform to limit prompt and response retention for a regulated application. 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—assume disabling application logs eliminates all copies in supporting systems—does not establish the required control for a SaaS procurement platform to limit prompt and response retention for a regulated application. 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 684
At a municipal services portal, engineers need to support document lineage for generated answers. Monitoring should isolate failures to the responsible component. A recent review found that the current design has no reliable safeguard for this case. Which design decision addresses the underlying issue?
- Store stable source identifiers, revision timestamps and permissions alongside chunks
- Discard all source identifiers after vectorization
- Use anonymous embeddings with no reference to original documents
- Ask the language model to invent document revision IDs
Explanation
Correct Answer
A:Chunk metadata supports traceability, filtering and source updates. In a municipal services portal, the engineering team should verify this design against its stated objective to support document lineage for generated answers, including the requirement that monitoring should isolate failures to the responsible component.
Incorrect Answers
B:The suggested action—discard all source identifiers after vectorization—does not establish the required control for a municipal services portal to support document lineage for generated answers. The change is applied outside the component responsible for the requirement identified by a municipal services portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—use anonymous embeddings with no reference to original documents—does not establish the required control for a municipal services portal to support document lineage for generated answers. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a municipal services portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—ask the language model to invent document revision IDs—does not establish the required control for a municipal services portal to support document lineage for generated answers. It replaces a verifiable engineering control with an untested shortcut in the a municipal services portal deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 685
At a telecom support operation, engineers need to add an auditable text-generation endpoint to a legacy application. The architecture must avoid unnecessary coupling between components. The initial assessment isolates this issue from unrelated infrastructure changes. Which remediation addresses the root problem?
- Give the legacy client direct unrestricted model credentials
- Send all requests through an unauthenticated public Lambda URL
- Replace the legacy database with prompt output
- Expose a validated API contract via API Gateway and a secured integration backend
Explanation
Correct Answer
D:An API facade enables authorization, throttling, versioning and consistent integration. In a telecom support operation, the engineering team should verify this design against its stated objective to add an auditable text-generation endpoint to a legacy application, including the requirement that the architecture must avoid unnecessary coupling between components.
Incorrect Answers
A:The suggested action—give the legacy client direct unrestricted model credentials—does not establish the required control for a telecom support operation to add an auditable text-generation endpoint to a legacy application. The change is applied outside the component responsible for the requirement identified by a telecom support operation. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—send all requests through an unauthenticated public Lambda URL—does not establish the required control for a telecom support operation to add an auditable text-generation endpoint to a legacy application. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a telecom support operation. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—replace the legacy database with prompt output—does not establish the required control for a telecom support operation to add an auditable text-generation endpoint to a legacy application. It replaces a verifiable engineering control with an untested shortcut in the a telecom support operation deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 686
At a regional insurer, engineers need to reduce cost for simple classifications while retaining advanced reasoning for exceptions. A controlled rollout is required before broad user exposure. The initial assessment isolates this issue from unrelated infrastructure changes. Which implementation most directly satisfies the requirement?
- Cascade from a smaller capable model to a stronger model when confidence or policy requires
- Invoke the most expensive model for every trivial request
- Lower every response quality threshold to minimize invocation counts
- Change the vector index instead of the inference policy
Explanation
Correct Answer
A:Model cascading makes expensive inference conditional on measured task difficulty. In a regional insurer, the engineering team should verify this design against its stated objective to reduce cost for simple classifications while retaining advanced reasoning for exceptions, including the requirement that a controlled rollout is required before broad user exposure.
Incorrect Answers
B:The suggested action—invoke the most expensive model for every trivial request—does not establish the required control for a regional insurer to reduce cost for simple classifications while retaining advanced reasoning for exceptions. The change is applied outside the component responsible for the requirement identified by a regional insurer. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
C:The suggested action—lower every response quality threshold to minimize invocation counts—does not establish the required control for a regional insurer to reduce cost for simple classifications while retaining advanced reasoning for exceptions. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a regional insurer. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—change the vector index instead of the inference policy—does not establish the required control for a regional insurer to reduce cost for simple classifications while retaining advanced reasoning for exceptions. It replaces a verifiable engineering control with an untested shortcut in the a regional insurer deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 687
At a municipal services portal, engineers need to publish an internal GenAI service with an explicit, testable API schema. A controlled rollout is required before broad user exposure. The initial assessment isolates this issue from unrelated infrastructure changes. Which design decision addresses the underlying issue?
- Let consumers guess request parameters from generated examples
- 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
Explanation
Correct Answer
C:API-first contracts reduce ambiguous integration and support compatibility testing. In a municipal services 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—let consumers guess request parameters from generated examples—does not establish the required control for a municipal services portal to publish an internal GenAI service with an explicit, testable API schema. The change is applied outside the component responsible for the requirement identified by a municipal services 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 the vector dimension as the API version—does not establish the required control for a municipal services 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 municipal services portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—describe the API exclusively in unversioned prompt instructions—does not establish the required control for a municipal services portal to publish an internal GenAI service with an explicit, testable API schema. The change is applied outside the component responsible for the requirement identified by a municipal services portal. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 688
At a digital publishing business, engineers need to provide a lightweight stateless capability to a remote agent. The team must preserve existing identity and authorization boundaries. The team wants a solution that can be validated through targeted test cases. Which design decision addresses the underlying issue?
- Build a separate foundation model for each tool
- Store persistent state only in a Lambda process global
- Expose an authenticated MCP-compatible tool endpoint backed by Lambda where appropriate
- Grant the agent a blanket administrative session
Explanation
Correct Answer
C:MCP describes interoperable tool access; runtime deployment still requires secure authentication and suitable state handling. In a digital publishing business, the engineering team should verify this design against its stated objective to provide a lightweight stateless capability to a remote agent, including the requirement that the team must preserve existing identity and authorization boundaries.
Incorrect Answers
A:The suggested action—build a separate foundation model for each tool—does not establish the required control for a digital publishing business to provide a lightweight stateless capability to a remote agent. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a digital publishing business. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
B:The suggested action—store persistent state only in a Lambda process global—does not establish the required control for a digital publishing business to provide a lightweight stateless capability to a remote agent. It replaces a verifiable engineering control with an untested shortcut in the a digital publishing business deployment. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
D:The suggested action—grant the agent a blanket administrative session—does not establish the required control for a digital publishing business to provide a lightweight stateless capability to a remote agent. No demonstrated capability in this scenario guarantees that this step resolves the concern raised by a digital publishing business. In this deployment, engineers should verify the missing mechanism rather than assume the proposed step satisfies the acceptance conditions.
Question 689
At a pharmaceutical documentation team, engineers need to restrict retrieval to documents belonging to the requesting tenant. The implementation must remain maintainable across model upgrades. An architecture review has rejected fixes that only conceal the symptoms. Which architecture is best supported by the stated constraints?
- Filter citations only after unauthorized content is sent to the model
- Rely solely on a prompt saying do not reveal other tenants
- Index all tenants without an authorization boundary
- Attach tenant metadata and enforce server-side authorization filters at retrieval time
Explanation
Correct Answer
D:Authorization must constrain retrieved context before it reaches the generation request. In a pharmaceutical documentation team, the engineering team should verify this design against its stated objective to restrict retrieval to documents belonging to the requesting tenant, including the requirement that the implementation must remain maintainable across model upgrades.
Incorrect Answers
A:The suggested action—filter citations only after unauthorized content is sent to the model—does not establish the required control for a pharmaceutical documentation team to restrict retrieval to documents belonging to the requesting tenant. 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.
B:The suggested action—rely solely on a prompt saying do not reveal other tenants—does not establish the required control for a pharmaceutical documentation team to restrict retrieval to documents belonging to the requesting tenant. 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—index all tenants without an authorization boundary—does not establish the required control for a pharmaceutical documentation team to restrict retrieval to documents belonging to the requesting tenant. 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.
Question 690
At a SaaS procurement platform, engineers need to provide a lightweight stateless capability to a remote agent. A controlled rollout is required before broad user exposure. A recent review found that the current design has no reliable safeguard for this case. Which remediation addresses the root problem?
- Store persistent state only in a Lambda process global
- Expose an authenticated MCP-compatible tool endpoint backed by Lambda where appropriate
- Grant the agent a blanket administrative session
- Build a separate foundation model for each tool
Explanation
Correct Answer
B:MCP describes interoperable tool access; runtime deployment still requires secure authentication and suitable state handling. In a SaaS procurement platform, the engineering team should verify this design against its stated objective to provide a lightweight stateless capability to a remote agent, including the requirement that a controlled rollout is required before broad user exposure.
Incorrect Answers
A:The suggested action—store persistent state only in a Lambda process global—does not establish the required control for a SaaS procurement platform to provide a lightweight stateless capability to a remote agent. 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—grant the agent a blanket administrative session—does not establish the required control for a SaaS procurement platform to provide a lightweight stateless capability to a remote agent. 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—build a separate foundation model for each tool—does not establish the required control for a SaaS procurement platform to provide a lightweight stateless capability to a remote agent. 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.