LEARN. PRACTICE. GROW.Separate attribution from cost reduction
The fictional twelve-thousand-euro invoice contains six thousand direct to A, three thousand to B, and three thousand shared. Under a two-to-one rule, totals are eight thousand and four thousand. With an equal split they become seven thousand five hundred and four thousand five hundred. The invoice did not change. One team can show a lower charge without any global saving. Keep the rule, measurement source, and unallocated costs visible. Tags help identify ownership but do not independently decide allocation of shared networking, support, or monitoring services.
Compare the complete alternative
Moving from twelve thousand to nine thousand euros monthly appears to save three thousand. If the destination still needs five hundred for archives and seven hundred for support, net saving is eighteen hundred. Add twenty-one thousand six hundred of transition and six thousand of first-year overlap: the alternative costs one hundred and fifty thousand against the current one hundred and forty-four thousand. The example has higher first-year cost despite recurring benefit. These are teaching figures without tax or discounting; a real comparison should state horizon, prices, volume, and applicable charges.
Choose a unit representing value
A lower invoice can accompany less completed work. Twelve thousand euros for six hundred thousand operations gives two cents each; nine thousand for three hundred thousand gives three. Unit cost increased fifty percent. Define a useful operation and deduplicate attempts when the metric intends to count business outcomes. Keep unit and scope consistent across comparison. Optimization that removes reconciliation, recovery, or support can reduce price while changing the service. Before recommending that option, explain the difference and obtain evidence that requirements which remain applicable will still be met by the proposed alternative.
Assess exit as service reconstruction
Exporting data is a milestone rather than proof of destination continuity. List required configuration, keys, identities, integrations, tools, people, and contractual conditions. The July 2025 ECB guide discusses exit strategies and responsibilities; it is supervisory guidance with its own scope rather than certification awarded by this course. In the original model, six hundred GB at fifty GB per hour takes twelve hours. Five-hour configuration runs in parallel and three-hour validation follows: total fifteen. If the rate falls to twenty-five, duration becomes twenty-seven. No actual transfer was executed by this exercise.
Close dependencies before destroying capability
Retirement can leave seasonal consumers, retained information, or active costs. One month without traffic does not eliminate a known annual statement. An encrypted archive without sustainable key access can become unreadable. Resolve retention needs with competent owners and demonstrate authorized reading before removing dependencies. Then confirm access withdrawal, residual resources, and contractual charges. Stopping CPU neither deletes disks nor automatically terminates subscriptions. Use separate milestones for shutdown, information continuity, and financial closure so that a lifecycle with open work is not declared complete simply because its main server is inactive.
Present decisions with checkable assumptions
The workshop asks for three deliverables: a complete-cost matrix, an exit plan with dependencies, and a retirement evidence list. For each, identify observations, assumptions, and pending decisions. The local program verifies arithmetic and fictional conditions; it does not approve a change, measure migration, or establish regulatory conformance. All banking cases are original and do not describe BNP Paribas procedures. Meeting numerical question-bank lower targets does not replace specialist review or a facilitated workshop. Use the material to prepare discussions with FinOps, suppliers, APS, and the service owner about demonstrable outcomes.
OFICINA / WORKSHOP: 45 minutos / 45 minutes
Cenários fictícios; não usar credenciais, faturas ou dados bancários reais.
Fictional scenarios; do not use real credentials, invoices, or banking data.
0-8: Executar o código anterior / Run the preceding code:
python3 run.py --output evidence.json
Registar runtime, passed, runnerSha256 e limites do modelo.
Record runtime, passed, runnerSha256, and model limits.
8-18: Matriz de acesso / Access matrix:
ator / actor; ação / action; recurso / resource;
janela / window; referência / reference; revogação / withdrawal.
Explicar como demonstrar uma permissão e a sua retirada no sistema real.
Explain how to demonstrate a grant and its withdrawal in the real system.
18-28: Matriz de custos / Cost matrix:
old=12000/month; destination=9000; archive=500; support=700
transition=21600; overlap=6000
recurring saving=1800/month; year-one difference=-6000 benefit
Assinalar hipóteses que precisariam de fonte e aprovação.
Mark assumptions needing evidence and approval.
28-38: Saída e retirada / Exit and retirement:
data export; configuration; keys; identities; integrations;
consumers; retention; readable archive; access; residual billing.
Classificar cada linha: demonstrada, assumida ou pendente.
Classify each row: demonstrated, assumed, or pending.
38-45: Redigir em inglês / Write in English:
Recommendation / observed evidence / unresolved dependencies /
budget impact / accountable owner / next acceptance checkpoint.
Não apresentar este modelo como IAM AWS ou migração executada.
Do not present this model as AWS IAM or an executed migration.
The alternative saves a net €1800/month, but transition and overlap make year one €6000 more expensive in the example without discounting.
Common pitfalls
Allocation treated as saving, a lower invoice as guaranteed efficiency, export as complete exit, or a stopped machine as closure of every charge.
Related topics: Identity, connectivity, and protection · Change, obsolescence, and decommissioning · Cloud, costs, and RUN autonomy
The lifecycle is explained only when cost, continuity, retained information, access, and residual charges have evidence and ownership.
Reference: Allocation · BigSavant banking infrastructure professional assessment2026.10