Book Image

Exam Ref AZ-304 Microsoft Azure Architect Design Certification and Beyond

By : Brett Hargreaves
Book Image

Exam Ref AZ-304 Microsoft Azure Architect Design Certification and Beyond

By: Brett Hargreaves

Overview of this book

The AZ-304 exam tests an architect's ability to design scalable, reliable, and secure solutions in Azure based on customer requirements. Exam Ref AZ-304 Microsoft Azure Architect Design Certification and Beyond offers complete, up-to-date coverage of the AZ-304 exam content to help you prepare for it confidently, pass the exam first time, and get ready for real-world challenges. This book will help you to investigate the need for good architectural practices and discover how they address common concerns for cloud-based solutions. You will work through the CloudStack, from identity and access through to infrastructure (IaaS), data, applications, and serverless (PaaS). As you make progress, you will delve into operations including monitoring, resilience, scalability, and disaster recovery. Finally, you'll gain a clear understanding of how these operations fit into the real world with the help of full scenario-based examples throughout the book. By the end of this Azure book, you'll have covered everything you need to pass the AZ-304 certification exam and have a handy desktop reference guide.
Table of Contents (30 chapters)
1
Section 1: Exploring Modern Architecture
4
Section 2: Identity and Security
9
Section 3: Infrastructure and Storage Components
14
Section 4: Applications and Databases
19
Section 5: Operations and Monitoring
23
Section 6: Beyond the Exam
26
Mock Exam
27
Mock Answers

Chapter 17

As part of the overall solution, you could leverage Azure DevOps tooling as this is built specifically for development teams and aligns to agile and Scrum practices.

All code will be stored in a central repository for the project. A master branch will always contain fully working and tested code, and at the start of each sprint, two branches will be created for each team.

As developers work on tasks, they will create their own separate branch for their work, and once finished, they will create a pull request to have their individual code merged into the sprint branch. The senior developer on each team will review each pull request from the junior team members and approve as required, which will trigger a merge into the sprint branch.

At the end of the sprint, the individual sprint branches will be tested, validated, and then merged into the master branch prior to deployment.

The pipeline deployment will be built as YAML files as this allows the pipeline configuration...