A retailer with branch stores wants a weekly view of store experience, because leadership cannot use a separate page for every interface flap. Which deliverable fits that audience?
Select an answer to reveal the explanation.
Short Explanation
Leadership reads the weekly weather, not every raindrop that hit a store. You give executives a weekly experience trend that rolls branch flaps into a pattern they can use. A live flap board, a support packet, or a transaction trace serves a different desk.
Full Explanation
An executive weekly trend of branch-store experience summarizes interface flaps into one score leadership can read without a separate page for each event. The request was for a weekly view, and a page per flap is the format this audience already said it cannot use. Operators still need a live board that lists each flap as it opens and clears, because that is how a network operations desk works a shift. A production-support handoff pairs an open alert with the latest tests, which is the packet for people working one incident rather than a weekly pattern. An application-team trace isolates the transaction step stores cannot finish, which matters to the people who own the application and not to a leadership readout. The exam trap is handing executives the same live flap board the operations desk uses and calling that board a summary. In production, check that the weekly pack contains one experience trend for the branches and does not attach a separate page for each interface flap. Keep the live board, the incident packet, and the transaction trace available to their own audiences so the executive view stays a trend.