Question 330
Engineering reports that a feature passes its tests, but operations rejects it because exception handling is unusable. No business acceptance owner was named. What process change best prevents recurrence?
- Assign an acceptance owner and agree on operational criteria before implementation
- Require operations to accept every feature that passes engineering tests
- Let acceptance depend on whichever stakeholder reviews the feature last
- Add more unit tests without revisiting the intended user workflow
Explanation
Correct Answer
A:Technical checks and operational acceptance answer related but different questions. An explicit owner and agreed criteria bring exception handling into the definition of completion.
Incorrect Answers
B:Engineering tests may omit essential workflow requirements. Imposing acceptance would conceal the missing criteria rather than resolve them.
C:That creates unstable decision authority and late surprises. Ownership and criteria should be established before the implementation is treated as complete.
D:Additional tests help only if they represent the right requirements. The stated failure is missing operational acceptance criteria and ownership.
Question 331
A pilot requires access to a partner API whose approval may take six weeks. The plan assumes access on day one and schedules dependent work immediately. What should change?
- Treat a mock API as proof that production access is already available
- Make the dependency explicit and plan useful work and milestones around its uncertainty
- Remove the partner integration from status reports until access is granted
- Ask developers to work faster to absorb the approval delay
Explanation
Correct Answer
B:An unresolved external approval can determine the schedule. The plan should expose that dependency and identify work that can proceed without pretending access is guaranteed.
Incorrect Answers
A:A mock can unblock some development but does not establish authorization or production connectivity. The remaining dependency must stay explicit.
C:Omitting the dependency prevents stakeholders from understanding schedule risk. Visibility is necessary for escalation and informed planning.
D:Engineering effort cannot directly eliminate an external approval dependency. The schedule needs a realistic treatment of the prerequisite.
Question 332
An architecture assumes that every incoming document has a stable customer identifier, but this has not been verified. What is the best way to manage the assumption?
- Wait for a production failure to reveal whether it matters
- Record it with an owner, validation task, deadline, and consequence if false
- Remove the assumption from the design to keep the document concise
- Treat it as a requirement because the proposed design depends on it
Explanation
Correct Answer
B:A material assumption should be testable and tracked before dependent commitments become expensive. Its failure impact guides validation priority and contingency planning.
Incorrect Answers
A:The condition can be checked before deployment. Waiting unnecessarily exposes the project to a known and potentially consequential uncertainty.
C:Hiding the premise leaves the dependency in place without visibility. Concision should not obscure a condition that can invalidate the architecture.
D:A design dependency does not make an assumption true. The source data must be examined or the workflow changed to satisfy the requirement.
Question 333
An executive must decide whether to fund a pilot. The technical team presents only token counts and orchestration diagrams. What additional framing is most useful?
- Connect the proposed workflow to expected value, principal risks, evidence, and the funding decision
- Replace the technical presentation with a longer glossary of model terminology
- Show every implementation detail so the executive can choose individual components
- Report only the most favorable benchmark result to simplify the message
Explanation
Correct Answer
A:The executive needs to understand the consequences and uncertainty of the investment. Technical details should support that decision rather than stand alone.
Incorrect Answers
B:Terminology can help comprehension but does not establish value or risk. The investment decision still lacks a business-oriented evidence summary.
C:Component selection may be delegated to technical owners. The funding decision needs the overall case and material risks at the appropriate level.
D:Selective evidence can misrepresent readiness and uncertainty. A useful decision brief includes relevant limitations and trade-offs.
Question 334
A pilot must determine whether retrieval improves analyst accuracy. Stakeholders also request voice input, billing integration, and a redesigned portal. What scope best supports the pilot's purpose?
- All requested features, because a broader release always produces stronger evidence
- A retrieval benchmark with no analyst interaction despite workflow-dependent goals
- The smallest usable workflow that can measure the retrieval hypothesis under representative conditions
- A production rollout to every analyst before measuring baseline performance
- Only the redesigned portal because it is easiest for stakeholders to see
Explanation
Correct Answer
C:The pilot should include what is necessary to test its stated uncertainty. Unrelated features add work and confounding changes without strengthening that evidence.
Incorrect Answers
A:Broader scope can delay learning and obscure which change caused an outcome. Completeness is not the same as a well-designed pilot.
B:An isolated benchmark may omit how analysts use and interpret results. The pilot needs enough workflow realism to measure the intended outcome.
D:A broad rollout increases exposure without first resolving the pilot's question. It also complicates comparison if no baseline was established.
E:Visibility does not make the portal relevant to the retrieval hypothesis. The pilot's scope should follow the decision it is meant to inform.
Question 335
One enthusiastic user requests a feature, while support data shows a frequent failure affecting many core tasks. Both compete for the next sprint. How should the team prioritize?
- Implement the newest request because recent feedback is always more relevant
- Assign equal effort to every request regardless of affected users
- Implement whichever request includes the most detailed proposed solution
- Compare impact, frequency, strategic fit, and effort using an agreed prioritization process
Explanation
Correct Answer
D:Feedback should be evaluated against the product's goals and observed effects. A transparent process prevents a single vocal request from automatically displacing widespread needs.
Incorrect Answers
A:Recency alone does not establish value or urgency. A long-standing frequent failure may have much greater impact on the core workflow.
B:Equal allocation ignores differences in impact and relevance. The team should make explicit trade-offs rather than treat all requests as equivalent.
C:A detailed proposal can still address a low-priority problem. Prioritization should assess the need and effect, not merely the sophistication of the suggested design.
Question 336
A pilot costs 12,000 to implement and is expected to produce 3,000 in monthly benefit after monthly operating costs. Ignoring discounting and ramp-up, what is the simple payback period?
- One quarter, because there are three months in a reporting cycle
- Four months
- It cannot be calculated without a separate monthly API bill
- Twelve months, because implementation cost is usually annualized
Explanation
Correct Answer
B:The setup investment is recovered through net monthly benefit. Dividing 12,000 by 3,000 gives four months under the scenario's simplifying assumptions.
Incorrect Answers
A:The reporting calendar does not determine investment recovery. Three months of the stated net benefit would recover only 9,000.
C:The scenario already states benefit after monthly operating costs. A separate API bill would double-count a cost already included in the net figure.
D:Annual accounting presentation does not change this simple cash recovery calculation. The given net monthly benefit recovers the stated investment in four months.
Question 337
An assistant saves staff ten hours per week, but staffing and contractor payments remain unchanged. How should the initial benefit be described in a business case?
- An immediate reduction in payroll equal to ten hours of average salary
- Freed capacity, with cash savings claimed only if an actual cost reduction follows
- A permanent ten-hour saving regardless of future volume or review requirements
- The full project cost recovered in the first week without a cost comparison
- No benefit of any kind because the payroll remains unchanged
Explanation
Correct Answer
B:Reduced task effort is valuable but does not automatically reduce spending. The business case should distinguish time available for other work from realized financial savings.
Incorrect Answers
A:The stated payroll has not changed. Valuing time can inform an economic estimate, but it should not be reported as a realized cash reduction.
C:The observed benefit depends on operating conditions. A lasting claim should account for changes in workload, adoption, and any additional responsibilities.
D:The time result alone does not establish payback. Recovery of investment requires a consistent valuation and comparison with the project's costs.
E:Freed capacity can improve throughput, service, or future hiring needs. The absence of immediate cash savings does not make the time improvement worthless.
Question 338
A purchased assistant meets the core workflow but cannot support a mandatory data-location requirement. A custom implementation can meet it at higher cost. What should the decision process do first?
- Build the custom option without documenting cost or operating responsibilities
- Treat the location requirement as a feasibility gate before comparing remaining trade-offs
- Average the location failure with the purchased product's stronger convenience score
- Buy the product because existing features always outweigh custom development risk
Explanation
Correct Answer
B:A mandatory constraint determines whether an option is acceptable. Cost and convenience can be compared among feasible choices or after an authorized change to the requirement.
Incorrect Answers
A:Feasibility does not remove the need to assess the viable option's cost and ownership. The decision still needs an informed implementation and operating plan.
C:A weighted average can conceal failure of a mandatory condition. The requirement cannot be traded away without the appropriate decision to change it.
D:Existing features are valuable only if the option can satisfy the required deployment constraints. The location gap remains material.
Question 339
A pilot is funded as a one-time innovation project. Production would require recurring evaluation, support, and model usage, but no owner has accepted those costs. What must be resolved before rollout?
- Delay discussion until the first production invoice arrives
- Assign an operating owner and fund the recurring service responsibilities
- Charge all future expenses to the closed pilot budget automatically
- Assume usage savings will pay for support without estimating either
Explanation
Correct Answer
B:Production requires ongoing work beyond the pilot's initial funding. Explicit ownership and budget make the proposed service sustainable and accountable.
Incorrect Answers
A:That creates an avoidable ownership gap after deployment. Recurring responsibilities should be accepted before the service is broadly relied upon.
C:A completed one-time budget does not establish funding authority for recurring costs. The organization needs an explicit operating commitment.
D:Potential savings do not guarantee available operating funds. The decision needs a credible cost model and accountable budget owner.
Question 340
A vendor announces that an API behavior used by the application will change in three months. What lifecycle response is most appropriate?
- Wait until users report failures to determine which dependencies matter
- Assess affected dependencies, validate a migration, and schedule rollout before the change
- Freeze the local code and assume the remote behavior will remain unchanged
- Immediately migrate every integration without testing compatibility
Explanation
Correct Answer
B:A known external change creates a planning window. The team should identify impact and test the adaptation rather than wait for production breakage.
Incorrect Answers
A:The dependency can be investigated before the deadline. Waiting discards the opportunity to reduce avoidable disruption.
C:A local freeze does not prevent a vendor-side change. The application still depends on the announced behavior and needs an impact assessment.
D:Urgency does not eliminate migration risk. The available window should be used for validation and an orderly rollout.