Worth saying what it is before judging it: not a book, but the official syllabus for a certification. It states what is expected of someone with two or three years building data pipelines, and splits the exam into four domains with weights: ingestion and transformation thirty-four per cent, storage and modelling twenty-six, operations and support twenty-two, security and governance eighteen.
What I took from it
Those percentages, read as what they are — a large vendor's judgement about where the work sits — serve as a checklist well outside their own world. When I review how a company moves its data, I now look at the four in roughly that proportion. What I usually find is the opposite of what the syllabus implies: all the effort spent moving data and none on operating it, with nobody finding out when a nightly job stopped running.
The second use is more concrete: the governance and security domain supplies vocabulary that works in a conversation with management. Catalogue, lineage, data lifecycle, who may see what. Those are the questions nobody asks until someone needs a record that has already been deleted.
What I left out
Everything else, which is a list of one vendor's services. A syllabus teaches you to recognise product names, not to solve problems; memorising which of two nearly identical services to pick is knowledge with an expiry date and no value off that platform. I did not read it to get certified and I would not recommend it as a source: read it in an afternoon, take the structure, close it.