Question 440
During a language-model integration rollout, two different failure paths need remediation. The first component must estimate whether a multilingual request will fit a model context window; separately, the second must explain why a plausible answer can still contain an unsupported factual claim. Which changes should be adopted?
- First component: Budget tokens rather than characters. Second component: Recognize next-token generation.
- First component: Use varied sampling only for ideation. Second component: Recognize next-token generation.
- First component: Understand context-window competition. Second component: Use varied sampling only for ideation.
- First component: Budget tokens rather than characters. Second component: Understand context-window competition.
Explanation
Correct Answer
A:The first proposal fits its assigned role because tokenization splits text into model-specific units, so character counts are not a reliable context proxy, while the second proposal fits its assigned role because the model predicts likely continuations conditioned on context rather than querying an authoritative truth database by default; their respective acceptance criteria are to estimate whether a multilingual request will fit a model context window and to explain why a plausible answer can still contain an unsupported factual claim.
Incorrect Answers
B:The first proposal serves the different purpose to brainstorm diverse naming candidates without demanding identical wording on every run instead of the assigned first role because greater sampling diversity can produce a wider range of suggestions for exploratory work, while the second proposal fits its assigned role because the model predicts likely continuations conditioned on context rather than querying an authoritative truth database by default; their respective acceptance criteria are to estimate whether a multilingual request will fit a model context window and to explain why a plausible answer can still contain an unsupported factual claim.
C:The first proposal serves the different purpose to avoid assuming retrieved material, tool outputs, history, and instructions each have independent infinite capacity instead of the assigned first role because all supplied content competes for a finite effective context budget and may affect attention, while the second proposal serves the different purpose to brainstorm diverse naming candidates without demanding identical wording on every run instead of the assigned second role because greater sampling diversity can produce a wider range of suggestions for exploratory work; their respective acceptance criteria are to estimate whether a multilingual request will fit a model context window and to explain why a plausible answer can still contain an unsupported factual claim.
D:The first proposal fits its assigned role because tokenization splits text into model-specific units, so character counts are not a reliable context proxy, while the second proposal serves the different purpose to avoid assuming retrieved material, tool outputs, history, and instructions each have independent infinite capacity instead of the assigned second role because all supplied content competes for a finite effective context budget and may affect attention; their respective acceptance criteria are to estimate whether a multilingual request will fit a model context window and to explain why a plausible answer can still contain an unsupported factual claim.
Question 441
A design review identifies a missing capability in a backend integration project: it must test whether document classification quality is viable on representative files. Which change meets that goal?
- Perform a threat review before go-live
- Define a staged release with rollback
- Use a proof of concept before production commitment
- Assign an owner to every integration
- Separate development, staging, and production environments
Explanation
Correct Answer
C:A small pilot reduces feasibility risk before funding a complete integration; this behavior directly supports the need to test whether document classification quality is viable on representative files. A presentation-only prototype cannot establish real input coverage.
Incorrect Answers
A:Reviewing trust boundaries and permissions before deployment reveals attack routes unit tests may miss; this applies to the different goal to uncover prompt-injection paths through retrieved webpages and connected tools, not the requirement to test whether document classification quality is viable on representative files; a post-incident review cannot prevent the initial exposure.
B:When an application needs to deploy a prompt change without exposing every customer to an untested regression, gradual rollout and versioned rollback allow metrics to be compared while limiting impact; the current capability must instead test whether document classification quality is viable on representative files, while editing the only production prompt in place makes reversions harder.
D:This approach serves the separate need to prevent abandoned connectors from retaining access after an application is transferred because ownership enables rotation, monitoring, change approval, and retirement decisions; it does not establish the outcome to test whether document classification quality is viable on representative files, and an undocumented connector can remain privileged beyond its operational need.
E:Environment boundaries keep credentials, data, and writes isolated during testing; despite being useful when a service must exercise an agent's database tool without touching live customer records, it is not a solution to test whether document classification quality is viable on representative files; reusing production tokens in a local experiment defeats the separation.
Question 442
An output validation team owns two independent components. The first must prevent a negative invoice total from reaching a payment ledger; the second must prevent the frontend from parsing an incomplete JSON chunk as a complete response. Which paired plan fulfills both?
- First component: Escape generated content in the UI. Second component: Validate required schema fields.
- First component: Validate semantic business invariants. Second component: Separate a partial streaming fragment from a finished object.
- First component: Validate required schema fields. Second component: Parse JSON with a real parser.
- First component: Parse JSON with a real parser. Second component: Separate a partial streaming fragment from a finished object.
- First component: Validate semantic business invariants. Second component: Validate required schema fields.
Explanation
Correct Answer
B:The first proposal fits its assigned role because domain rules check value ranges and cross-field relationships beyond syntactic shape, while the second proposal fits its assigned role because stream consumers must buffer and recognize completion before strict object validation; their respective acceptance criteria are to prevent a negative invoice total from reaching a payment ledger and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
Incorrect Answers
A:The first proposal serves the different purpose to show model-produced HTML snippets without allowing browser script injection instead of the assigned first role because output encoding or sanitization protects display contexts from untrusted markup, while the second proposal serves the different purpose to reject a response that omits a mandated account identifier instead of the assigned second role because schema checks enforce field presence, types, and enumerations before the result enters a database; their respective acceptance criteria are to prevent a negative invoice total from reaching a payment ledger and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
C:The first proposal serves the different purpose to reject a response that omits a mandated account identifier instead of the assigned first role because schema checks enforce field presence, types, and enumerations before the result enters a database, while the second proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned second role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds; their respective acceptance criteria are to prevent a negative invoice total from reaching a payment ledger and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
D:The first proposal serves the different purpose to avoid accepting malformed generated objects because they resemble JSON to a reader instead of the assigned first role because syntax validation converts serialized text into a trustworthy data structure only after parsing succeeds, while the second proposal fits its assigned role because stream consumers must buffer and recognize completion before strict object validation; their respective acceptance criteria are to prevent a negative invoice total from reaching a payment ledger and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
E:The first proposal fits its assigned role because domain rules check value ranges and cross-field relationships beyond syntactic shape, while the second proposal serves the different purpose to reject a response that omits a mandated account identifier instead of the assigned second role because schema checks enforce field presence, types, and enumerations before the result enters a database; their respective acceptance criteria are to prevent a negative invoice total from reaching a payment ledger and to prevent the frontend from parsing an incomplete JSON chunk as a complete response.
Question 443
During an agent extensibility rollout, two different failure paths need remediation. The first component must deny destructive filesystem operations before a coding agent executes them; separately, the second must make a coding or API assistant follow organization-wide conventions. Which changes should be adopted?
- First component: Package a Skill for reusable guidance. Second component: Publish an MCP server for reusable integrations.
- First component: Publish an MCP server for reusable integrations. Second component: Use system or repository instructions for stable behavior.
- First component: Use hooks for enforceable safety checks. Second component: Use system or repository instructions for stable behavior.
- First component: Use hooks for enforceable safety checks. Second component: Package a Skill for reusable guidance.
Explanation
Correct Answer
C:The first proposal fits its assigned role because runtime interception can apply deterministic policies to proposed actions, while the second proposal fits its assigned role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to deny destructive filesystem operations before a coding agent executes them and to make a coding or API assistant follow organization-wide conventions.
Incorrect Answers
A:The first proposal serves the different purpose to give a coding agent a consistent review playbook and supporting assets instead of the assigned first role because a Skill provides task procedures and resources that the agent can load when applicable, while the second proposal serves the different purpose to make one internal ticketing connector available to several agent clients instead of the assigned second role because MCP standardizes tool and resource discovery across compatible applications; their respective acceptance criteria are to deny destructive filesystem operations before a coding agent executes them and to make a coding or API assistant follow organization-wide conventions.
B:The first proposal serves the different purpose to make one internal ticketing connector available to several agent clients instead of the assigned first role because MCP standardizes tool and resource discovery across compatible applications, while the second proposal fits its assigned role because instructions shape model behavior and task framing without executing external operations; their respective acceptance criteria are to deny destructive filesystem operations before a coding agent executes them and to make a coding or API assistant follow organization-wide conventions.
D:The first proposal fits its assigned role because runtime interception can apply deterministic policies to proposed actions, while the second proposal serves the different purpose to give a coding agent a consistent review playbook and supporting assets instead of the assigned second role because a Skill provides task procedures and resources that the agent can load when applicable; their respective acceptance criteria are to deny destructive filesystem operations before a coding agent executes them and to make a coding or API assistant follow organization-wide conventions.
Question 444
An inference routing team owns two independent components. The first must contain cumulative token and tool cost across a recursive research session; the second must reduce repeated processing of identical tool definitions and system instructions. Which paired plan fulfills both?
- First component: Measure cache read tokens. Second component: Set budget alerts and tenant caps.
- First component: Set budget alerts and tenant caps. Second component: Cache a stable shared prefix.
- First component: Set maximum step counts for agents. Second component: Cache a stable shared prefix.
- First component: Set maximum step counts for agents. Second component: Measure cache read tokens.
- First component: Shorten irrelevant conversation history. Second component: Measure cache read tokens.
Explanation
Correct Answer
C:The first proposal fits its assigned role because a bound on iterations prevents repeated generation and calls from growing without limit, while the second proposal fits its assigned role because prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match; their respective acceptance criteria are to contain cumulative token and tool cost across a recursive research session and to reduce repeated processing of identical tool definitions and system instructions.
Incorrect Answers
A:The first proposal serves the different purpose to verify that an optimization actually reuses an earlier prompt prefix instead of the assigned first role because usage fields show how much eligible cached input was read rather than recomputed, while the second proposal serves the different purpose to stop a single customer from consuming the entire API allowance during a runaway workflow instead of the assigned second role because accounting plus enforced limits bounds exposure to unexpected traffic and agent loops; their respective acceptance criteria are to contain cumulative token and tool cost across a recursive research session and to reduce repeated processing of identical tool definitions and system instructions.
B:The first proposal serves the different purpose to stop a single customer from consuming the entire API allowance during a runaway workflow instead of the assigned first role because accounting plus enforced limits bounds exposure to unexpected traffic and agent loops, while the second proposal fits its assigned role because prefix caching can lower repeated-input cost when the eligible prefix and cache conditions match; their respective acceptance criteria are to contain cumulative token and tool cost across a recursive research session and to reduce repeated processing of identical tool definitions and system instructions.
D:The first proposal fits its assigned role because a bound on iterations prevents repeated generation and calls from growing without limit, while the second proposal serves the different purpose to verify that an optimization actually reuses an earlier prompt prefix instead of the assigned second role because usage fields show how much eligible cached input was read rather than recomputed; their respective acceptance criteria are to contain cumulative token and tool cost across a recursive research session and to reduce repeated processing of identical tool definitions and system instructions.
E:The first proposal serves the different purpose to reduce token spend without losing facts needed for the current request instead of the assigned first role because selective context assembly preserves active constraints while removing obsolete turns, while the second proposal serves the different purpose to verify that an optimization actually reuses an earlier prompt prefix instead of the assigned second role because usage fields show how much eligible cached input was read rather than recomputed; their respective acceptance criteria are to contain cumulative token and tool cost across a recursive research session and to reduce repeated processing of identical tool definitions and system instructions.
Question 445
A release plan for an application security platform has two acceptance checks: component one must limit the impact of a temporary worker credential being stolen; component two must deny access to a different customer's records even when the caller is authenticated. Which proposal passes both?
- First component: Rotate a compromised API key promptly. Second component: Protect secrets in error traces.
- First component: Protect secrets in error traces. Second component: Authorize by requested resource and action.
- First component: Use short-lived scoped credentials where supported. Second component: Rotate a compromised API key promptly.
- First component: Use short-lived scoped credentials where supported. Second component: Authorize by requested resource and action.
Explanation
Correct Answer
D:The first proposal fits its assigned role because expiring identity grants reduce the time and permissions available to an attacker, while the second proposal fits its assigned role because authorization checks must evaluate scope for each operation, not only whether a login exists; their respective acceptance criteria are to limit the impact of a temporary worker credential being stolen and to deny access to a different customer's records even when the caller is authenticated.
Incorrect Answers
A:The first proposal serves the different purpose to cut off an exposed token discovered in CI logs instead of the assigned first role because revocation plus replacement ends use of the leaked credential and requires checking for misuse, while the second proposal serves the different purpose to prevent stack traces and debugging telemetry from disclosing tokens instead of the assigned second role because redaction at logging boundaries avoids accidentally copying credentials to broad observability systems; their respective acceptance criteria are to limit the impact of a temporary worker credential being stolen and to deny access to a different customer's records even when the caller is authenticated.
B:The first proposal serves the different purpose to prevent stack traces and debugging telemetry from disclosing tokens instead of the assigned first role because redaction at logging boundaries avoids accidentally copying credentials to broad observability systems, while the second proposal fits its assigned role because authorization checks must evaluate scope for each operation, not only whether a login exists; their respective acceptance criteria are to limit the impact of a temporary worker credential being stolen and to deny access to a different customer's records even when the caller is authenticated.
C:The first proposal fits its assigned role because expiring identity grants reduce the time and permissions available to an attacker, while the second proposal serves the different purpose to cut off an exposed token discovered in CI logs instead of the assigned second role because revocation plus replacement ends use of the leaked credential and requires checking for misuse; their respective acceptance criteria are to limit the impact of a temporary worker credential being stolen and to deny access to a different customer's records even when the caller is authenticated.
Question 446
A production-readiness check for a token economics component requires the service to clarify a specific formatting convention that a plain instruction was not conveying. Which approach passes this check?
- Budget tokens rather than characters
- Treat model outputs as stochastic
- Reduce reasoning effort on trivial routing
- Use one representative example
Explanation
Correct Answer
D:A single demonstration can anchor the expected shape and tone of a generated response; this behavior directly supports the need to clarify a specific formatting convention that a plain instruction was not conveying. An example is not a formal guarantee that every response will conform.
Incorrect Answers
A:Tokenization splits text into model-specific units, so character counts are not a reliable context proxy; this applies to the different goal to estimate whether a multilingual request will fit a model context window, not the requirement to clarify a specific formatting convention that a plain instruction was not conveying; equal-length strings can have different token usage.
B:When an application needs to design tests that tolerate benign wording variation while detecting semantic failures, non-determinism requires evaluation by criteria and repeated examples rather than exact-string equality everywhere; the current capability must instead clarify a specific formatting convention that a plain instruction was not conveying, while a single run is insufficient to prove robust model behavior.
C:Lower effort can suit predictable work where deeper reasoning adds little measurable quality; the supported outcome is to shorten latency and spend on tasks that need only basic categorization, whereas this scenario requires the ability to clarify a specific formatting convention that a plain instruction was not conveying; using maximum effort for every request wastes resources.
Question 447
Engineers are splitting an application security service into two independently tested functions. Function A must reduce automated abuse of a model-backed export or search capability, while function B must inspect proposed scripts without granting them production host privileges. Which plan is sound?
- First component: Require verified identity for privileged actions. Second component: Sandbox generated code execution.
- First component: Run adversarial prompt-injection tests. Second component: Require verified identity for privileged actions.
- First component: Rate-limit high-risk endpoints. Second component: Run adversarial prompt-injection tests.
- First component: Rate-limit high-risk endpoints. Second component: Sandbox generated code execution.
Explanation
Correct Answer
D:The first proposal fits its assigned role because per-identity quotas and anomaly monitoring make bulk misuse harder, while the second proposal fits its assigned role because resource, filesystem, and network isolation contain failures and malicious effects; their respective acceptance criteria are to reduce automated abuse of a model-backed export or search capability and to inspect proposed scripts without granting them production host privileges.
Incorrect Answers
A:The first proposal serves the different purpose to stop an unauthenticated user from invoking a dangerous account-management tool instead of the assigned first role because authentication establishes the caller before authorization policies consider requested permissions, while the second proposal fits its assigned role because resource, filesystem, and network isolation contain failures and malicious effects; their respective acceptance criteria are to reduce automated abuse of a model-backed export or search capability and to inspect proposed scripts without granting them production host privileges.
B:The first proposal serves the different purpose to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools instead of the assigned first role because purposeful hostile test cases probe whether the trust boundary holds under manipulated evidence, while the second proposal serves the different purpose to stop an unauthenticated user from invoking a dangerous account-management tool instead of the assigned second role because authentication establishes the caller before authorization policies consider requested permissions; their respective acceptance criteria are to reduce automated abuse of a model-backed export or search capability and to inspect proposed scripts without granting them production host privileges.
C:The first proposal fits its assigned role because per-identity quotas and anomaly monitoring make bulk misuse harder, while the second proposal serves the different purpose to find vulnerabilities in a retrieval-augmented assistant before it accesses production tools instead of the assigned second role because purposeful hostile test cases probe whether the trust boundary holds under manipulated evidence; their respective acceptance criteria are to reduce automated abuse of a model-backed export or search capability and to inspect proposed scripts without granting them production host privileges.
Question 448
An architecture review of a tool integration product lists two distinct outcomes: the first subsystem must stop a directory lookup function from also gaining unrestricted database write access, and a second subsystem must identify whether slow agent replies come from a payment gateway rather than the model. Which pair delivers these outcomes?
- First component: Separate read tools from write tools. Second component: Define narrow tool input schemas.
- First component: Define narrow tool input schemas. Second component: Capture tool latency and failure metrics.
- First component: Restrict tool network credentials. Second component: Capture tool latency and failure metrics.
- First component: Restrict tool network credentials. Second component: Separate read tools from write tools.
Explanation
Correct Answer
C:The first proposal fits its assigned role because minimal capabilities reduce risk when generated arguments or retrieved text are hostile, while the second proposal fits its assigned role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; their respective acceptance criteria are to stop a directory lookup function from also gaining unrestricted database write access and to identify whether slow agent replies come from a payment gateway rather than the model.
Incorrect Answers
A:The first proposal serves the different purpose to require stricter approval for actions that change customer data instead of the assigned first role because distinct interfaces simplify least-privilege grants and side-effect controls, while the second proposal serves the different purpose to prevent ambiguous generated arguments from reaching an inventory service instead of the assigned second role because typed parameter definitions constrain requests and enable strict validation before execution; their respective acceptance criteria are to stop a directory lookup function from also gaining unrestricted database write access and to identify whether slow agent replies come from a payment gateway rather than the model.
B:The first proposal serves the different purpose to prevent ambiguous generated arguments from reaching an inventory service instead of the assigned first role because typed parameter definitions constrain requests and enable strict validation before execution, while the second proposal fits its assigned role because per-tool tracing separates external execution time from inference and highlights unhealthy dependencies; their respective acceptance criteria are to stop a directory lookup function from also gaining unrestricted database write access and to identify whether slow agent replies come from a payment gateway rather than the model.
D:The first proposal fits its assigned role because minimal capabilities reduce risk when generated arguments or retrieved text are hostile, while the second proposal serves the different purpose to require stricter approval for actions that change customer data instead of the assigned second role because distinct interfaces simplify least-privilege grants and side-effect controls; their respective acceptance criteria are to stop a directory lookup function from also gaining unrestricted database write access and to identify whether slow agent replies come from a payment gateway rather than the model.
Question 449
During acceptance testing for a customer platform service, one requirement is to keep follow-up requests linked without exposing another tenant's messages. What should the developer implement?
- Create one session per user conversation
- Design an explicit escalation path
- Keep user tasks in the user message
- Add cancellation handling to streaming UI
Explanation
Correct Answer
A:Session scoping ensures history and tool results belong to the correct principal; this behavior directly supports the need to keep follow-up requests linked without exposing another tenant's messages. A global conversation list risks mixing private records.
Incorrect Answers
B:Risk-based thresholds separate assistance from decisions reserved for accountable staff; this applies to the different goal to route uncertain medical-style recommendations to an authorized human instead of issuing final decisions, not the requirement to keep follow-up requests linked without exposing another tenant's messages; increasing model confidence language is not a control for consequential actions.
C:When an application needs to separate an end user's request from the developer's stable operating instructions, explicit message roles distinguish requested work from higher-priority operational framing; the current capability must instead keep follow-up requests linked without exposing another tenant's messages, while merging everything into one unstructured prompt weakens provenance.
D:Cancellation signals should propagate through streams, queues, and workers where supported; the supported outcome is to stop processing when a user cancels a long report and release resources cleanly, whereas this scenario requires the ability to keep follow-up requests linked without exposing another tenant's messages; hiding the browser output alone may leave paid requests running.
Question 450
The acceptance criteria for an application security change state that it must protect payload confidentiality between the application and its API endpoint. Which implementation aligns with that criterion?
- Apply retention limits to diagnostic logs
- Encrypt sensitive data in transit
- Minimize personally identifiable information
- Validate tool arguments server-side
Explanation
Correct Answer
B:Modern transport encryption limits interception across network boundaries; this behavior directly supports the need to protect payload confidentiality between the application and its API endpoint. Merely obfuscating a prompt is not transport security.
Incorrect Answers
A:Data minimization and controlled retention reduce the duration and audience of sensitive log content; this applies to the different goal to reduce exposure of customer documents copied into application telemetry, not the requirement to protect payload confidentiality between the application and its API endpoint; an internal log is still a data store requiring access controls.
C:Redaction and selective fields reduce exposure before data enters model or logging paths; the supported outcome is to avoid transmitting unnecessary customer identifiers with a summarization request, whereas this scenario requires the ability to protect payload confidentiality between the application and its API endpoint; logging every full prompt can defeat otherwise careful minimization.
D:This approach serves the separate need to block a generated database query that targets another tenant's records because backend authorization checks must bind the requested operation to the caller's entitlements; it does not establish the outcome to protect payload confidentiality between the application and its API endpoint, and well-formed arguments are not proof of permission.