> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/self-check-module-2.md). # Self-check — Module 2 Four questions on what a manager decides, drawn from the single messages of module 2. **Module 2 — Break the service down before you design it.** Answer each question before you read the answer beside it. Four questions for the manager who commissions the service, each drawn from the single messages of the module. Each has one right answer, given with the reason, so that a reader can check their own understanding without a tutor. The questions are written for the written guide and for the additional materials proposed for the final delivery; they are not read aloud in any video. | # | Question | Choices | Answer, and why | Drawn from | | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | | 1 | A donor offers to fund a new licensing system for your quality authority. What do you ask for before the first specification is approved? | A. A list of the screens the new system will have. B. The sector's catalogue: every service the sector's bodies owe, with the shared blocks each one rests on. C. The supplier's price for the licensing system alone. | B. Only the catalogue shows which blocks many services rest on, so that a block is planned for the sector and not rebuilt by each project. | 2.1 | | 2 | The supplier's table of goals against the register of what was asked has a row with no mark. What does it tell you? | A. A goal that nobody asked for. B. Something that was asked, in the customer's words and with its source, that no goal will deliver. C. Nothing; empty rows are normal in a first design. | B. Each entry is one thing asked, with where it was said, and every entry must be served by a goal. The empty row becomes a question with an owner and a date. | 2.2, 2.4 | | 3 | The ministry's draft design keeps its own copy of each institution's name, and the authority's draft design writes the application fee into a screen as a figure. What do you require? | A. Nothing; copies make the ministry faster. B. The name read from the authority's register, and the fee read from a setting with an owner, or raised as a question. C. A monthly check that the copies still agree. | B. For every fact the service keeps it, takes it from another body or must not hold it; settings are written once, with an owner, and a goal that needs a missing one raises a question. | 2.3, 2.5 | | 4 | The software architecture lists a crossing to the ministry that the ministry has not seen. What do you do before you accept the page? | A. Accept it; the ministry can object later. B. Have the ministry confirm its row before you accept. C. Remove the crossing from the page. | B. The page names every flow that crosses to another body, and each row is agreed with the body on the other side; until then it is a promise made on their behalf. | 2.6 | Back to [Module 2](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/self-check-module-2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.