You're reading from Exam Ref AZ-304 Microsoft Azure Architect Design Certification and Beyond

Product type Book

Published in Jul 2021

Publisher Packt

ISBN-13 9781800566934

Pages 520 pages

Edition 1st Edition

Languages

Concepts

Cloud Computing

Author (1):

Brett Hargreaves

Table of Contents (30) Chapters

Preface

1. Section 1: Exploring Modern Architecture

2. Chapter 1: Architecture for the Cloud

3. Chapter 2: Principles of Modern Architecture

4. Section 2: Identity and Security

5. Chapter 3: Understanding User Authentication

6. Chapter 4: Managing User Authorization

7. Chapter 5: Ensuring Platform Governance

8. Chapter 6: Building Application Security

9. Section 3: Infrastructure and Storage Components

10. Chapter 7: Designing Compute Solutions

11. Chapter 8: Network Connectivity and Security

12. Chapter 9: Exploring Storage Solutions

13. Chapter 10: Migrating Workloads to Azure

14. Section 4: Applications and Databases

15. Chapter 11: Comparing Application Components

16. Chapter 12: Creating Scalable and Secure Databases

17. Chapter 13: Options for Data Integration

18. Chapter 14: High Availability and Redundancy Concepts

19. Section 5: Operations and Monitoring

20. Chapter 15: Designing for Logging and Monitoring

21. Chapter 16: Developing Business Continuity

22. Chapter 17: Scripted Deployments and DevOps Automation

23. Section 6: Beyond the Exam

24. Chapter 18: Engaging with Real-World Customers

25. Chapter 19: Enterprise Design Considerations

26. Mock Exam

27. Mock Answers

28. Assessments

29. Other Books You May Enjoy

Connectivity

A simple, standalone solution may only require a single VNET, and especially if your service is an externally facing application for clients, you may not need to create anything more complicated.

However, for enterprise applications that contain many different services, or for hybrid scenarios where you need to connect securely to Azure from an on-premises network, you must consider the other options for providing connectivity.

We will start by looking at connecting two VNETs.

Previously, we separated services within different subnets. However, each of those subnets was in the same subnet. Because of this, connectivity between the devices was automatic – other than defining NSG rules, connectivity just happened.

More complex solutions may be built across multiple VNETs, and these VNETs may or may not be in the same region. By default, communication between VNETs is not enabled. Therefore you must set this up if required. The simplest way to achieve this connectivity...