Question 310
A policy says, 'If the customer opts in, send a reminder.' The customer has not opted in. What should an action extractor preserve?
- A conclusion that reminders are always forbidden.
- An inference that reading the policy counts as opting in.
- The reminder action together with its unsatisfied opt-in precondition.
- An unconditional instruction to send the reminder now.
Explanation
Correct Answer
C:Conditional extraction must retain the trigger that determines when the action becomes applicable. The extractor can represent an action as conditional without scheduling it immediately. Losing the opt-in condition would turn a description of policy into an unauthorized operational instruction.
Incorrect Answers
A:The policy permits reminders when the stated condition is satisfied.
B:The source gives no basis for treating policy access as customer consent.
D:Removing the condition changes the policy into an action it does not currently authorize.
Question 311
A prompt contains dozens of legacy style rules that conflict with the new requested output format. What is the best maintenance approach?
- Remove obsolete rules, state the current contract clearly, and test representative cases.
- Choose whichever output format appears in the most recent example without revising the conflicting rules.
- Append another rule saying all earlier rules are mandatory.
- Keep adding examples without deciding which format is supported.
Explanation
Correct Answer
A:A coherent prompt and regression evidence reduce accidental behavior from accumulated instructions. A prompt should express the supported format in one coherent place where possible. Regression cases then test whether removing legacy rules changes any behavior that must remain.
Incorrect Answers
B:An implicit example-based preference leaves the written contract inconsistent and fragile.
C:Reasserting incompatible rules leaves the output contract contradictory.
D:Examples cannot reliably resolve an undefined precedence among conflicting requirements.
Question 312
A policy states, 'A project lead may request an architecture review.' A generated summary says, 'Every project lead must request an architecture review.' What correction preserves the policy's meaning?
- State that a review has already occurred because the policy permits requesting one.
- Keep the mandatory wording because stronger instructions are easier for readers to follow.
- State that architecture reviews are prohibited unless the policy uses the word must.
- Describe the review request as permitted, without inventing a universal obligation.
Explanation
Correct Answer
D:May grants permission in this statement; must would impose a requirement. The summary should preserve that difference instead of strengthening the policy.
Incorrect Answers
A:Permission to request an action does not establish that it happened. This would convert a rule about allowed behavior into an unsupported event claim.
B:Ease of execution does not justify changing the policy's force. A summary must not create an obligation absent from its source.
C:An optional permission is not a prohibition. The policy explicitly allows the lead to request a review.
Question 313
A long-context prompt contains background documents but never states the question the output should answer. What is the most important correction?
- Require the model to infer the user's private motivation.
- Increase the response length without specifying a target.
- State the concrete question, required evidence, and desired answer structure.
- Add more documents until the purpose becomes obvious.
Explanation
Correct Answer
C:An explicit task directs attention within the large context toward a testable output. Background provides evidence, while the question defines what to do with it. Specifying the requested comparison or decision prevents an expensive but unfocused general summary.
Incorrect Answers
A:An unstated personal motivation cannot be reliably recovered from background text.
B:A longer response can remain irrelevant when the question is undefined.
D:Additional background does not define the missing analytical objective.
Question 314
An application's JSON Schema includes a keyword unsupported by the selected structured-output feature. Which TWO steps are appropriate? Choose TWO.
- Express supported constraints in the schema and enforce any remaining required checks in application code.
- Assume every JSON Schema keyword is supported because JSON itself is accepted.
- Retry the identical unsupported schema indefinitely.
- Check the feature's supported schema subset for the chosen model and API configuration.
- Remove every validation rule without assessing its purpose.
Explanation
Correct Answers
A:A divided validation design can retain the intended contract when some constraints cannot be expressed in the generation feature.
D:Compatibility must be established against the actual structured-output interface in use.
Incorrect Answers
B:Support for JSON output does not imply support for the full schema specification.
C:A deterministic schema limitation is not fixed by repeated submission.
E:Discarding the contract wholesale loses useful guarantees that may still be supported.
Question 315
A downstream parser rejects unexpected fields, but generated objects include helpful commentary under new keys. What should the output contract do?
- Disallow undeclared properties where supported and provide any necessary commentary through declared fields.
- Put commentary into the middle of numeric values.
- Ask the parser to ignore its own contract without versioning the change.
- Encourage arbitrary additional keys for every explanation.
Explanation
Correct Answer
A:A closed field set keeps generated output compatible while explicitly accommodating permitted explanation. A consumer cannot reliably distinguish business fields from ad hoc helpful commentary. Declaring the permitted place for explanation preserves usefulness without breaking a closed object contract.
Incorrect Answers
B:Embedding prose in numbers breaks types instead of defining a valid place for commentary.
C:Silently weakening the consumer does not establish a clear interface agreement.
D:Uncontrolled properties remain incompatible with the strict downstream parser.
Question 316
A classifier's allowed statuses change from open/closed to open/resolved/canceled. What must be updated together?
- Only the examples, while leaving the schema enum and consumer unchanged.
- Nothing, because any string is equivalent to any status.
- Only the model's role description.
- The output schema, prompt definitions, examples, and consuming logic for the revised status set.
Explanation
Correct Answer
D:All parts of the contract must agree on the new meanings and valid values. Older stored records may also need an explicit mapping or migration policy. Introducing new labels in the prompt alone can produce values that the schema rejects or the consumer misinterprets.
Incorrect Answers
A:Updated demonstrations can generate statuses that the unchanged interface still rejects.
B:Status values carry distinct semantics and are not interchangeable arbitrary text.
C:A persona change does not define or migrate the enumeration.
Question 317
An output contains "quantity": "12 units" while the consumer requires an integer quantity and a separate unit field. What is the correct contract?
- Treat every numeric-looking string as a valid integer without parsing.
- Store both fields in the quantity string and abandon validation.
- Remove the unit from all source documents before processing them.
- Represent quantity as 12 and units in the declared unit field, validating both.
Explanation
Correct Answer
D:Separate typed fields preserve the measurement and satisfy the consumer's expected data structure. A numeric quantity supports arithmetic and comparison without string parsing. Units remain necessary metadata, but they should not be embedded in a field promised to contain an integer.
Incorrect Answers
A:The string includes nonnumeric text and violates the declared integer interface.
B:An unvalidated compound string shifts ambiguity to every downstream consumer.
C:Destroying source information is unnecessary when the output can represent value and unit separately.
Question 318
A consumer reads the second property of a JSON object as the customer ID. The producer emits the same valid fields in a different order. What should be fixed?
- Read the customer ID by its property name rather than positional order.
- Convert every property to an array element without documenting positions.
- Read whichever value matches the usual customer-ID pattern, ignoring the property name.
- Treat a different property order as evidence that the values are false.
Explanation
Correct Answer
A:Object properties are identified by keys, so reordering should not change field interpretation. A name-based parser remains correct when an encoder changes property order. If ordering itself matters to the task, it should be represented by an appropriate explicit structure rather than object position.
Incorrect Answers
B:An undocumented array would preserve positional ambiguity rather than define a stable interface.
C:Other fields can share the pattern, so value guessing is weaker than the explicit keyed contract.
D:Reordering alone does not change the named fields' factual content.
Question 319
An output can represent either a successful extraction or an unresolved case needing review. What structure best prevents ambiguous combinations?
- A free-text paragraph that sometimes includes the word success.
- A supported tagged outcome structure with explicit success and needs_review variants.
- A flat object with many unrelated optional fields and no status.
- A boolean whose meaning changes depending on field order.
Explanation
Correct Answer
B:A clear discriminator lets the consumer interpret each outcome using its corresponding fields. Each variant can define the fields that make sense for that outcome. A needs-review result should not be forced to fabricate success fields simply to satisfy a flat object shape.
Incorrect Answers
A:Unstructured wording is a fragile discriminator for a machine-consumed result.
C:The consumer cannot reliably determine which fields belong to which outcome.
D:Field-order-dependent meaning is an unstable and undocumented interface.
Question 320
A task requires exactly three distinct candidate titles. The output contains three array entries, two identical. What must validation include?
- Only whether the array uses square brackets.
- Both the required entry count and a meaningful distinctness check.
- A rule to repeat the best title until three slots are filled.
- Only whether the first entry is nonempty.
- Count three entries as three candidates whenever their capitalization differs, even when all three express the same underlying title.
Explanation
Correct Answer
B:Array length alone does not ensure that the three entries represent different candidates. Distinctness should match the task's intent rather than only byte differences. Capitalization or punctuation variants of one title may still be the same candidate for this purpose.
Incorrect Answers
A:Valid array syntax says nothing about its cardinality or duplicate values.
C:Repeated entries defeat the explicit requirement for distinct candidates.
D:One nonempty item does not establish the required count or uniqueness.
E:Surface differences can satisfy string inequality without providing meaningful alternatives. Distinctness must follow the user's requirement for different candidate titles.