Book Image

Azure Data and AI Architect Handbook

By : Olivier Mertens, Breght Van Baelen
Book Image

Azure Data and AI Architect Handbook

By: Olivier Mertens, Breght Van Baelen

Overview of this book

With data’s growing importance in businesses, the need for cloud data and AI architects has never been higher. The Azure Data and AI Architect Handbook is designed to assist any data professional or academic looking to advance their cloud data platform designing skills. This book will help you understand all the individual components of an end-to-end data architecture and how to piece them together into a scalable and robust solution. You’ll begin by getting to grips with core data architecture design concepts and Azure Data & AI services, before exploring cloud landing zones and best practices for building up an enterprise-scale data platform from scratch. Next, you’ll take a deep dive into various data domains such as data engineering, business intelligence, data science, and data governance. As you advance, you’ll cover topics ranging from learning different methods of ingesting data into the cloud to designing the right data warehousing solution, managing large-scale data transformations, extracting valuable insights, and learning how to leverage cloud computing to drive advanced analytical workloads. Finally, you’ll discover how to add data governance, compliance, and security to solutions. By the end of this book, you’ll have gained the expertise needed to become a well-rounded Azure Data & AI architect.
Table of Contents (18 chapters)
1
Part 1: Introduction to Azure Data Architect
4
Part 2: Data Engineering on Azure
8
Part 3: Data Warehousing and Analytics
13
Part 4: Data Security, Governance, and Compliance

Network security

Much like IAM, networking and network security are huge domains. The exact network security configurations are often best kept for experts in the field, but it is still valuable for a cloud data architect to grasp the principles of securing networks.

The PoLP in access management stated that any identity should have the least amount of access to complete the job. Similar to this, in network security, endpoints should have the least possible exposure.

First, this comes down to not blindly opening up all endpoints to the public internet. This is, however, the default option in many Azure services. It is possible to deny public network access on the resource level, or we could enforce any resource of a given type to have disabled public network access by using Azure Policy. Azure Policy is further explained at the end of this chapter.

By disabling all access from the public network, the resources can only be accessed through private endpoints. This prevents...