Study for this assessment by learning the concepts themselves — Agenda 2063 versus the SDGs, output versus outcome, concessional versus non-concessional financing logic, risk versus assumption, and integrity standards — and practicing short paper scenarios where you must choose and justify an option. Verify application logistics and program details on the AfDB careers page; this guide focuses on the underlying subject matter and a practice sequence you can adapt.
Distinguishing the frameworks: High 5s, Agenda 2063, and the SDGs
Three frameworks overlap but are not interchangeable: the SDGs are global, Agenda 2063 is the African Union's continental vision, and the High 5s are the Bank's operational priority areas. Practicing the mapping between them builds the precision that scenario answers demand.
The High 5s — Light up and power Africa, Feed Africa, Industrialize Africa, Integrate Africa, and Improve the quality of life for the people of Africa — are sector-level priorities used to organize the Bank's operational focus. Agenda 2063, by contrast, is a fifty-year continental aspiration owned by the African Union, with its own aspirations and flagship projects. These are easy to blur because they share vocabulary — prosperity, integration, industrialization — while differing in owner, time horizon, and function. A regional power pool or cross-border corridor, for example, can be described through all three framings at once.
A useful drill: take any development intervention — a solar mini-grid, a staple-crop value chain, a customs harmonization program — and write one sentence for how it maps to each of the three frameworks. If you cannot produce distinct sentences, you are treating the frameworks as synonyms. That distinctness matters in scenario answers because justifying an option usually requires naming the right framework and explaining what it contributes that the others do not.
The practical exercise later in this guide includes a framework-mapping step with a rubric you can use to check your own mappings.
- SDGs: global goals with universal targets and indicators.
- Agenda 2063: African Union continental vision with aspirations and flagship projects.
- High 5s: Bank operational priorities spanning energy, agriculture, industrialization, integration, and quality of life.
Reading development indicators without over-reading them
Indicators describe conditions; they do not by themselves justify a decision. Practice pairing each indicator with what it can and cannot support — for example, GNI per capita informs income classification, not project quality or institutional capacity.
When you practice with country snapshots — income per capita, sector shares, access rates, growth trends — train yourself to interpret under constraints. A low income level tells you about eligibility for concessional terms in broad strokes, but it tells you little about whether a specific power project is well designed. Strong GDP growth says nothing about distribution, fragility, or fiscal space. Make a habit of stating explicitly what each indicator supports and what it does not before you use it to favor an option.
Build a two-column habit for every indicator you encounter in news or reports: 'suggests' and 'does not show.' For example, rising mobile penetration suggests digital delivery may be feasible; it does not show affordability for poor households. Also separate composite from single measures: a composite index summarizes several dimensions and hides trade-offs, while a single indicator is transparent but narrow. Naming that distinction in a scenario answer is stronger than citing either number alone.
Concessional versus non-concessional financing logic: a worked scenario
Financing-window reasoning matches concessionality to the borrower's circumstances and the project's character. The tempting mistake in scenarios is matching terms to project sector instead of to country circumstances and debt considerations.
The Bank group operates both non-concessional lending and a concessional window serving lower-income regional member countries. Worked scenario: a lower-income country with limited fiscal space proposes a rural electrification program with long payback periods. A plausible mistake is recommending the non-concessional window because 'infrastructure generates growth.' The stronger reasoning recognizes that highly concessional terms exist precisely for low-income contexts where commercial terms could create debt stress or make socially valuable projects unaffordable — then justifies the recommendation on those grounds.
Flip the scenario: a creditworthy middle-income country seeks financing for a revenue-generating toll road. Recommending the concessional window here would be the weaker answer, since the project's cash flows and the country's circumstances support ordinary terms, and concessional resources are a scarce public good better reserved for contexts that need them. Practice writing a two-sentence justification for each direction — country circumstances, then project cash-flow character. Keep your certainty honest: real window allocation involves detailed eligibility criteria and policies; treat this scenario logic as a learning model, not a claim about specific country allocations.
| Concept pair | Distinguishing question | If you cannot answer it |
|---|---|---|
| Output vs outcome | Does this describe delivery of the intervention, or a change in beneficiaries' behavior or conditions? | You will build monitoring plans that measure activity, not change. |
| Outcome vs impact | Is this the near-term change the project influences, or the longer-term, higher-level change it contributes to? | Your causal chain will jump from delivery to grand ambitions with no middle. |
| Risk vs assumption | Is this an external factor we accept as broadly true (assumption), or an uncertain event we monitor and mitigate (risk)? | Your project logic will hide fragile links behind vague optimism. |
| Concessional vs non-concessional window logic | Do the country's circumstances and the project's cash flows support below-market or ordinary terms? | Financing recommendations will be matched to sector habit rather than to context. |
Results chains: outputs, outcomes, and the mislabeled step
A results chain runs inputs, activities, outputs, outcomes, and impact. The classic labeling error is calling a delivery-level item — such as people trained — an outcome. Outcomes describe changes in behavior or conditions.
Worked scenario: a monitoring exercise gives you '500 extension officers trained' and 'farmer adoption of improved seed rising' and asks which is the outcome. The plausible mistake is selecting the training figure because it sounds like achievement. The better decision identifies the training as an output — a direct, countable product of activities — and the adoption change as an outcome, because it reflects changed behavior among the intended beneficiaries and depends on assumptions beyond the project's direct control.
The distinction matters because labeling determines how you monitor and attribute. Outputs are verified by delivery records; outcomes require measurement of change and honest treatment of attribution. If you are asked how to strengthen measurement, the answer differs by level — delivery verification for outputs, baseline-and-endline comparison plus consideration of alternative explanations for outcomes. Mislabeling collapses that structure and produces monitoring plans that cannot distinguish success from mere activity.
Methods and documentation: logframes, risks, and assumptions
Documentation questions test whether you can structure project logic: a logframe links each level of the results chain to indicators, means of verification, and explicit assumptions about what must hold true outside the project's control.
Practice reading a logframe column by column. The vertical logic checks causality: activities should produce outputs, outputs plus assumptions should produce outcomes, outcomes plus assumptions should produce impact. The horizontal logic checks measurement: each level needs an indicator, a source of verification, and realistic targets. A common drafting weakness is an indicator that measures the level below — for example, using 'number of boreholes drilled' as the indicator for an outcome about household water access. Drilling more boreholes is not the same as households actually using better water.
Risk and assumption work is where documentation discipline becomes visible. An assumption is something you must believe for the chain to hold — fuel stays available, participating ministries keep staff in post — while a risk is an identified uncertainty you can monitor and mitigate. A good self-test: for each assumption, ask what evidence would make you stop believing it. If the answer is 'none, we just hope,' it is an unmanaged risk written in assumption language. When drafting your own logframe in practice, keep verbs level-consistent: activities use doing-verbs, outputs use delivered-nouns, outcomes use changed-conditions phrasing.
Ethics and integrity scenarios: choosing the defensible action
Integrity scenarios reward the option that protects the institution's decision-making process: disclose conflicts, route procurement concerns through official channels, and document the issue rather than resolving it privately.
Worked scenario: a colleague who is advising a supplier bid evaluation mentions at lunch that one bidder 'will do well.' You hold no formal role in the evaluation. The plausible mistake is staying silent because reporting feels accusatory and you might have misheard. The stronger decision is to raise the observation with the appropriate channel promptly and factually — what was said, when, by whom — letting the process, not your personal judgment, determine the outcome. Integrity systems depend on information flowing to the people accountable for decisions; private resolution defeats that design.
A second pattern to rehearse: the conflict of interest you did not create. If a relative works for a firm bidding on work adjacent to your assignment, the defensible action is disclosure, not self-assessment that you can 'stay objective.' Disclosure converts a hidden problem into a managed one and lets others reassign or screen as needed. Practice stating the principle first — protect the decision process — then the action, then the rationale; that three-part structure keeps ethics answers from becoming vague appeals to honesty.
A four-week practice sequence with readiness checks
Spend week one mapping frameworks and institutions, week two on results chains and logframes, week three on financing and ethics scenarios, week four on mixed timed practice — then verify readiness against observable outputs, not feelings.
Week one: build a one-page concept map linking the High 5s, Agenda 2063, and the SDGs, plus the Bank group's basic institutional structure and windows. Week two: draft two full results chains with logframe columns from real projects you read about. Week three: write ten two-sentence financing justifications and five ethics answers using the principle-action-rationale structure. Week four: combine everything into timed scenario practice where you must identify the concept, choose an option, and justify it without notes.
Practical exercise with a rubric: choose a current African infrastructure or agriculture project from news coverage and produce (1) a framework mapping, (2) a five-level results chain, (3) one risk and one assumption, and (4) a two-sentence financing-term reasoning. Score yourself: two points per element where the level labels are correct and the justifications are specific; one point where they are partially right. A learning milestone of roughly eight or more points means your concept boundaries are holding under unstructured material — this is a self-check, not a prediction of any exam result. Before you finish, run these readiness checks: you can state the High 5s without notes and give one distinct example per priority; you can label ten mixed results-chain items correctly; you can write a financing justification for either direction of concessionality; you can produce the three-part ethics structure for an unfamiliar scenario. If any check fails, return to that section's drill rather than rereading passively. For application procedures, eligibility, and program logistics, rely on the AfDB careers page rather than third-party summaries.
- Week 1: frameworks and institutions concept map.
- Week 2: two full results chains with logframes.
- Week 3: financing and ethics scenario drills.
- Week 4: timed mixed practice, then rubric self-scoring.
- Readiness = five observable outputs, each checkable in minutes.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.