Benjamin Perkins - Microsoft Azure Architect Technologies and Design Complete Study Guide: Exams AZ-303 and AZ-304

1. Introduction
2. Chapter 1
3. Chapter 2
4. Chapter 3
5. Chapter 4
6. Chapter 5
7. Chapter 6
8. Chapter 7
9. Chapter 8
10. Chapter 9

1. Chapter 1
2. Chapter 2
3. Chapter 3
4. Chapter 4
5. Chapter 5
6. Chapter 6
7. Chapter 7
8. Chapter 8
9. Chapter 9

Benjamin Perkins

Copyright 2021 by John Wiley & Sons, Inc., Indianapolis, Indiana

Published simultaneously in Canada

ISBN: 978-1-119-55953-5

ISBN: 978-1-119-55955-9 (ebk)

ISBN: 978-1-119-55957-3 (ebk)

No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at www.wiley.com/go/permissions.

Limit of Liability/Disclaimer of Warranty: The publisher and the author make no representations or warranties with respect to the accuracy or completeness of the contents of this work and specifically disclaim all warranties, including without limitation warranties of fitness for a particular purpose. No warranty may be created or extended by sales or promotional materials. The advice and strategies contained herein may not be suitable for every situation. This work is sold with the understanding that the publisher is not engaged in rendering legal, accounting, or other professional services. If professional assistance is required, the services of a competent professional person should be sought. Neither the publisher nor the author shall be liable for damages arising herefrom. The fact that an organization or Web site is referred to in this work as a citation and/or a potential source of further information does not mean that the author or the publisher endorses the information the organization or Web site may provide or recommendations it may make. Further, readers should be aware that Internet Web sites listed in this work may have changed or disappeared between when this work was written and when it is read.

For general information on our other products and services or to obtain technical support, please contact our Customer Care Department within the U.S. at (877) 762-2974, outside the U.S. at (317) 572-3993 or fax (317) 572-4002.

Wiley publishes in a variety of print and electronic formats and by print-on-demand. Some material included with standard print versions of this book may not be included in e-books or in print-on-demand. If this book refers to media such as a CD or DVD that is not included in the version you purchased, you may download this material at booksupport.wiley.com. For more information about Wiley products, visit www.wiley.com.

Library of Congress Control Number: 2020941635

TRADEMARKS: Wiley, the Wiley logo, and the Sybex logo are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates, in the United States and other countries, and may not be used without written permission. Microsoft is a registered trademark of Microsoft Corporation. All other trademarks are the property of their respective owners. John Wiley & Sons, Inc. is not associated with any product or vendor mentioned in this book.

Transforming an idea into content that can be consumed in a friendly and logical mannerrequires actions greater than the capacity of a single human being. The skillsets and experiences of a team do increase the reach, inclusiveness, and clarity of the subject being discussed. Here is a list of those who played a significant part in the creation of this book andthe organization of its content:

• Mary Ellen Schutz, project editor
• Barton Mathis, technical editor
• Rodney Fournier, technical editor
• Barath Kumar Rajasekaran, production editor
• Kim Wimpsett, copy editor
• Nancy Carrasco, proofreader
• Potomac Indexing, indexer

Writing this book was probably the most mentally challenging experience of my life. Ifnot the most, it is definitely in the top three. I want to call out my parents, Rual and DonnaPerkins, who raised me free from limits, free from critique, with maximum freedom ofchoice. You will come across people who tell you that you can't, but neither of them everuttered such a phrase to me. That time in my life gave me the strength I need now to overcome obstacles and finish the stuff I start, no matter what. I also need to call out my familywho continued to live life and carry on while I worked on this project. Andrea, Lea, andNoa, I thank you and love you from the bottom of my heart.

Benjamin Perkins is currently employed at Microsoft in Munich, Germany, as a senior escalation engineer for IIS, ASP.NET, and Azure App Services. He has been working professionally in the IT industry for more than two decades. He started computer programming with QBasic at the age of 11 on an Atari 1200XL desktop computer. He takes pleasure in the challenges that troubleshooting technical issues have to offer and savors in the rewards of a well-written program. After completing high school, he joined the United States Army. After successfully completing his military service, he attended Texas A&M University in College Station, Texas, where he received a bachelor's of business administration in management information systems. He also received a master's of business administration from the European University.

His roles in the IT industry have spanned the entire spectrum including programmer, system architect, technical support engineer, team leader, and mid- level management. While employed at Hewlett-Packard, he received numerous awards, degrees, and certifications. He has a passion for technology and customer service and looks forward to troubleshooting and writing more world-class technical solutions. My approach is to write code with support in mind, and to write it once correctly and completely so we do not have to come back to it again, except to enhance it.

Benjamin has written numerous magazine articles and training courses and is an active blogger. His catalog of books covers C# programming, IIS, NHibernate, open source, and Microsoft Azure.

• Connect with Benjamin on LinkedIn:

  www.linkedin.com/in/csharpguitar

• Follow Benjamin on Twitter:

  @csharpguitar -twitter.com/csharpguitar

• Read Benjamin's blog:

  www.thebestcsharpprogrammerintheworld.com