I'd easily consider this book's contents as required reading if you're working with Databricks on a daily basis, especially if you need to design architectures where Unity Catalog will be one of the central tenets.
The book not only provides the reader with a very good historical perspective, making the motivation and reasoning behind some current technical features clear, but it also presents how each feature fits together to provide a strong data platform foundation.
I've particularly liked the chapter on how to organize Unity Catalog for various levels of business complexity; how to make optimal use of the three-level namespace of catalogs, schemas, and data assets. On top of that, chapter organizing access control is another winner; it provides many different, concrete scenarios for Role Based Access Control (RBAC) and Fine Grained Access Control (FGAC). Linking these aspects to Workspace organization is another topic tackled in this book, which I'm sure to revisit.
When it comes to Databricks, it's not easy to go wide and deep, because the company constantly adds new features and what is today's limitation can be tomorrow's already-solved problem. Nevertheless, this book does almost a perfect job of organizing Databricks so that it can serve all sorts of team structures in differently sized companies.
If you need a deep dive on data engineering, orchestration, Python, etc. you'll need to find other resources but if you're really into designing and implementing the architecture of a data platform using Databricks, then you can't go wrong with this excellent book.