Book Image

Architecting Microsoft Azure Solutions - Exam Guide 70-535

By : Sjoukje Zaal
Book Image

Architecting Microsoft Azure Solutions - Exam Guide 70-535

By: Sjoukje Zaal

Overview of this book

Architecting Microsoft Azure Solutions: Exam Guide 70-535 will get Azure architects and developers up-to-date with the latest updates on Azure from an architecture and design perspective. The book includes all the topics that are still relevant from the previous 70-534 exam, and is updated with latest topics covered, including Artificial Intelligence, IoT, and architecture styles. This exam guide is divided into six parts, where the first part will give you a good understanding of how to design a compute infrastructure. It also dives into designing networking and data implementations. You will learn about designing solutions for Platform Service and operations. Next, you will be able to secure your resources and data, as well as design a mechanism for governance and policies. You will also understand the objective of designing solutions for Platform Services, by covering Artificial Intelligence, IoT, media services, and messaging solution concepts. Finally, you will cover the designing for operations objective. This objective covers application and platform monitoring, as well as designing alerting strategies and operations automation strategies. By the end of the book, you’ll have met all of the exam objectives, and will have all the information you need to ace the 70-535 exam. You will also have become an expert in designing solutions on Microsoft Azure.
Table of Contents (20 chapters)
Appendix A – Assessments
Appendix B – Mock Test Questions
Appendix C – Mock Test Answers

Azure Virtual Network

An Azure Virtual Network (VNet) is a virtual representation of a traditional network, hosted in the cloud. It is totally software-based, where traditional networks use cables, routers, and more. VNets provide a secure and isolated environment and they connect Azure resources with each other. By default, the different resources are not reachable from outside of the virtual network. You can, however, connect multiple VNets to each other or connect a VNet to your on-premises network as well. All the Azure resources that are connected inside the same VNet must reside in the same region and subscription.

When you create a VNet, one subnet is automatically created as well. You can create multiple subnets inside the same VNet (there is a maximum of 1000 subnets allowed per VNet). Connecting multiple VNets to each other is called virtual network peering. There is...