Book Image

Microsoft Azure Architect Technologies: Exam Guide AZ-300

By : Sjoukje Zaal
Book Image

Microsoft Azure Architect Technologies: Exam Guide AZ-300

By: Sjoukje Zaal

Overview of this book

From designing solutions on Azure to configuring and managing virtual networks, AZ-300 certification can help you achieve all this and more. Whether you want to get certified or gain hands-on experience in administering, developing, and architecting Azure solutions, this study guide will help you get started. The book features not only the different exam objectives, but also guides you through configuring, managing, securing, and architecting Azure resources. Divided into five modules, this book will systematically take you through the different concepts and features as you advance through the sections. The first module demonstrates how to deploy and configure infrastructure. You will cover techniques related to implementing workloads and security, before learning how to create and deploy apps in the next module. To build on your knowledge, the final two modules will get you up to speed with implementing authentication, data security, and application and platform monitoring, along with covering Azure storage, alerting, and automation strategies. Finally, you’ll work through exam-based mock tests with answers to boost your confidence in passing the exam. By the end of this book, you’ll have learned the concepts and techniques you need to know in order to prepare for the AZ-300 exam, along with the skills to design effective solutions on Microsoft Azure.
Table of Contents (30 chapters)
1
Section 1: Deploying and Configuring Infrastructure
9
Section 2: Implementing Workloads and Security
16
Section 3: Creating and Deploying Apps
19
Section 4: Implementing Authentication and Secure Data
22
Section 5: Developing for the Cloud and for Azure Storage
26
Mock Questions
27
Mock Answers

Understanding managed identities

One of the challenges, when you build applications for the cloud, is how to manage the credentials in code for authentication. Keeping those credentials secure is key, so ideally these credentials will never appear on developer workstations and aren't checked into source control as well. You can use Azure Key Vault for securely storing credentials, keys, and secrets, but the application still needs to authenticate to Key Vault to retrieve them.

Managed identities solves this problem. It is a feature of Azure AD, which provides Azure services with an automatically managed identity in Azure AD. You can then use this identity to authenticate to every server that supports Azure AD authentication, including Key Vault, without any credentials in your code.

When you enable managed identities on your Azure resource, such as a virtual machine, Azure Function, or app, Azure will create a service principal and store the credentials of that service principal...