Review questions

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

1. Question 1A clinic network is about to connect three booking systems. The interface is ready, but sites use different cancellation rules, and mistaken bookings will be costly to reverse. What should change first in the analysis approach?

   Analyze appointment states and cancellation rules with operations before a limited interface trial Build the interface immediately because technical readiness removes uncertainty Defer all analysis until the integration is finished Document every button and color before interviewing site staff
2. Question 2The operations director has approved an appointment screen. Shift staff say some slots are reserved for urgent referrals, and patients have not seen the model. What is the main engagement-plan gap?

   Not forwarding the approval to every director Not adding another technical workshop with developers Not asking patients to formally approve every site's booking policy Not hearing two affected groups whose knowledge the director's approval cannot replace
3. Question 3Two days before launch, one site manager asks to publish slots hidden under an approved network rule. Developers can implement the change in an hour. What is the controlled action?

   Record the difference, analyze effects on bookings and tests, and present options to the booking-policy authority Implement it because effort is less than a day Treat the site manager's request as approval for all sites Reject it permanently because an approved requirement can never change
4. Question 4Two files are named “Cancellation Rule.” One is approved for a site allowing cancellation up to 24 hours in advance; the other is a network draft including a service needing 48 hours. How should the information be managed?

   The newer file replaces the older because their names match Give each record an identifier, scope, version, and state; keep the site rule active until network approval Standardize on 24 hours because it was approved somewhere Delete the draft to avoid differing numbers
5. Question 5Average time to decide a rule rose from 6 to 11 days. Among 20 recent decisions, 12 waited for the policy owner, five reopened over different meanings of rescheduling, and three were technically delayed. What is the first improvement to test?

   Remove cancellation-rule review to reduce the average Schedule decisions with the policy owner and review an appointment-state model earlier, then measure time and reopening Add two general workshops weekly without changing policy-owner availability Treat technical delay as the cause of all twenty cases
6. Question 6A team wants to understand why employee expense claims stop. It has 30 records and four hours with staff. The manager proposes a general survey asking whether the system is bad. Which elicitation plan is strongest?

   Segment records by case type and time, then observe varied cases and interview an operator and approver about a recent stop Send only the survey because it can produce more answers Choose a new submit-button color and ask staff whether they like it Interview only the manager because they know the formal procedure
7. Question 7An employee says, 'We always approve large claims.' The analyst has observed one large claim referred to finance. What is the best elicitation follow-up?

   Why does your team break procedure? So should we add an automatic approval button? Can you recall the last case where 'always' did not apply, who decided, and what the system recorded? Do you agree that slow finance is the problem?
8. Question 8Management reports a two-day registration response time, while learners describe five days. Management starts timing after assigning a request to an employee, and some requests wait two days before assignment. What should first be confirmed?

   One party must be falsifying data The website form is the established cause Time from submission to first contact and time from assignment to contact should be calculated separately before judgment The official average is two days across all channels
9. Question 9Clinics approve hiding urgent slots from public search. The director needs a decision summary, while developers need a rule for unclassified slots. Which communication preserves meaning?

   Tell everyone 'hide urgent slots' and let developers decide unknown cases Show the director the decision's effects and developers a state table that withholds unknown slots until review Send every team full personal booking records Tell the director all slots will display so the offering looks complete
10. Question 10Marketing wants to hide refund conditions to increase registration completion; support records post-payment complaints caused by misunderstanding them. What is the most useful collaboration step?

    Remove refund conditions to end the disagreement Immediately choose the view of the higher-ranking person Add daily meetings without cases or measures Compare comprehension, completion, and complaints in a limited wording trial, then seek the policy owner's decision
11. Question 11A rule hiding urgent slots traces to a goal of fewer mistaken bookings and to an app display filter. There is an app test but none for another public interface reading appointment data. What did traceability reveal?

    Many links prove the solution works A test gap in another delivery path that might expose the slot The goal is no longer valid The app interface alone controls all bookings
12. Question 12An approved rule for a recorded course issues a certificate at 80% viewing. Someone wants to reuse it for a course that also requires a practical assignment. What is proper maintenance?

    Keep the old rule in its scope and propose a new version including the assignment after checking certificate purpose and authority Delete the old course version Issue the new certificate at 80%, then request the assignment later without saying so Copy it because it was previously approved
13. Question 13A release has 20 workdays. Nearest-slot display A takes 10, preventing accidental publication of urgent slots B takes 6 and is a prerequisite for A, and reminder C takes 8. Which set is feasible from these facts?

    A alone because B is invisible to users A, B, and C because each takes fewer than 20 days B then A, totaling 16 days with four unpromised days A and C because their visible value is higher even without B
14. Question 14An approved rule hides urgent-referral slots. A site manager proposes showing unused ones three hours before an appointment. What impact evidence is needed before approval?

    The number of colors to change Only the developer's view of how easy the condition is to code Total website visits without slot-type distinction How many slots truly remained unused, phone-booking concurrency, rule and test effects, and release authority
15. Question 15A training director verbally approved 'confirm seats quickly.' The specification now says 'confirm immediately after payment even if capacity has not updated.' Is it approved?

    Copy the old approval to the new version without a date The verbal phrase covers any faster wording No; present exhausted-capacity cases to the seat-policy owner for approval of a named version and conditions Developer approval is enough because developers implement it
16. Question 16A clinic's average wait is seven days. Half of ordinary requests book within two days, specialty referrals wait three weeks, and eligibility is reviewed manually twice a week. What is the best problem definition before choosing a solution?

    All patients suffer the same delay because a new app is missing Booking-page color causes the three-week wait Specialty referrals have a delay around a stage requiring data and review-rule analysis; the mean does not describe every group Eligibility review must be removed immediately
17. Question 17Clinics propose a future state of 'book every referral immediately.' Clinician capacity remains limited, but verification for complete cases can improve. Which future-state description is sound?

    Capture complete referral data, classify clear cases, escalate unknowns, and measure verification time with an error guard Promise instant booking for every case regardless of capacity Buy a booking portal before defining the rule Keep the current state because not every delay can be removed
18. Question 18In a sample of appointments, 15% of slots lack reliable classification. The team worries that an urgent slot may be shown publicly. Which risk interpretation is sound?

    Fifteen percent is the proven probability of a mistaken booking Unknown classification proves every slot is urgent There is no risk if the average number of displayed slots is high Missing classification is a current data constraint; accidental urgent display is a possible risk, reduced by withholding unknown slots and testing the source
19. Question 19An appointment-display trial works at a first site with immediate updates. A second site refreshes slot data every ten minutes. What is an appropriate transition condition?

    Copy the first site's plan because the screen is identical Measure update lag, test concurrent booking, and define a safe display state before wider publication Cancel the entire initiative because one site differs Launch every site on the announced date regardless of update lag
20. Question 20'Show available appointments' conceals slot type, viewer authority, and missing classification. Which representation best exposes the needed decision?

    A decision table combining slot type, viewer role, and display result, including unknown classification A screen description limited to color Only a stakeholder-name list Average monthly slot count
21. Question 21A requirement says, 'Show the nearest suitable appointment immediately.' What is the most relevant verification repair?

    Approve it because the words are familiar Estimate its financial value instead of editing it Replace immediately with quickly Define nearest, suitable, clock start, measurable limit, and tests for no slot and unknown classification
22. Question 22A blue booking button at the page top is precisely specified and testable. The goal is shorter referral waiting, but observed delay occurs in an eligibility queue before slot allocation. What is the validation judgment?

    Every interface requirement must be deleted Good wording proves the button meets the goal The value link is unsupported; test the queue cause or try the button for another evidenced goal Average wait alone proves blue will reduce it
23. Question 23After an urgent appointment is cancelled, an interface test releases its slot as ordinary, while operations requirements forbid public display of urgent slots. What is the architecture defect?

    The test is shorter than the text Cancellation-to-classification relation conflicts across views and needs a shared rule and cross-component test There is no issue because each statement can be read alone The operations view should be deleted
24. Question 24Clinics want shorter referral waits. A full public portal depends on incomplete slot classification; improved triage of current work does not; a hybrid shows only classified ordinary slots. What design step is sound?

    Design each option's colors before its behavior Choose the full portal because it uses more technology Choose the cheapest without examining referral cases Compare paths, constraints, burden, and value; test triage and then the hybrid if classification is reliable
25. Question 25Referral triage costs 40 units and cuts verification wait by four days. A portal costs 70 units and may reduce calls by 30%, but the referral share of calls is unknown. Which value recommendation is most defensible?

    Divide 30 by 70 and declare the portal's return higher Choose the costlier option because it has a new screen Trial triage against the observed bottleneck and test the portal narrowly to learn its actual call effect Add days, percentages, and cost units into one undefined score
26. Question 26Booking calls fell from 1,000 to 800, while total requests fell from 2,000 to 1,500. What is the most accurate conclusion about phone share?

    The portal is proven to have no users Share fell 20% because call count fell Share rose from 50% to about 53.3%; count alone does not prove movement to the portal Share stayed constant because both counts declined
27. Question 27After launch, 150 ordinary requests average three waiting days and 50 specialty referrals average eleven. How should the overall mean be read?

    Five days, while that mean may hide worsening specialty-referral service Three days because ordinary cases are more numerous Seven days because each group has equal weight Eleven days because specialty cases matter more
28. Question 28Patients saw a slot but could not book it. In seven of ten cases display data were five minutes old; in three another person booked after display. What is the solution-limitation diagnosis?

    Every case is normal competition Patients caused the fault by clicking slowly Remove booking without checking the integration boundary Internal update lag explains seven cases; measure it separately from genuine capacity competition
29. Question 29A system classifies referrals in minutes, but 70% then wait for a site director who signs only on Thursdays. Where is the likely value limitation?

    In classification-algorithm speed In decision authority and review cadence after the system's work, while the reason for control must be understood before changing it There is no limitation because the system is fast In the patient message color
30. Question 30Overall appointment waiting falls, but specialty referrals worsen, and their form may omit a required field. What first recommendation supports learning best?

    Remove all rules without reviewing approval authority Expand the portal to every slot now because the overall mean improved Declare network success because ordinary cases improved Repair referral data capture at one site and measure completeness and verification time with a mistaken-booking guard before expansion

Create a free account to mark your answers and save your progress.