later questions may jog your memory or give you a clue to something that you were stuck on earlier, so flag anything you are not sure about to come back to later. That said, some questions will not let you skip forward, as they could be part of a multiple-question scenario. The MS-700 exam will normally have at least one of these scenario sections that will be approximately 10 questions long.
Questions are traditionally multiple choice; however, there are several different formats that you might come across, including the following:
Build list
Active screen
Drag and drop
Case study
You can see the full list of possible question types at https://docs.microsoft.com/en-us/learn/certifications/certification-exams.
Case study questions aim to give you some real-world information that is then used across multiple questions. The information usually takes the form of paragraphs of information and then some supplementary data, such as tables, and so on. You can refer to this data as you need to during the subsequent questions. When answering case study questions, the text of the question will usually give you a specific clue about which part of the case study you should pay close attention to. For example, it might ask about what policy will meet the HR security requirements, in which case make sure you read the security requirement section closely.
You may also find some simulation or lab-based questions where you are given access to a sample environment and are expected to configure particular things. This is where having some real-world experience with Teams is helpful, as the chances are that it may look slightly different in real life than it does in books or training materials (because of the ever-evolving nature of the product). Simulation questions come in and out of favor, so you may not have any.
To pass the exam, you need to score at least 700 out of a possible 1,000 points available on the test; however, this does not directly correlate with a percentage-based score, as some questions can be weighted up or down. There is no distinction between passing with 700 points or full marks; a pass is a pass.
Don't just study the questions and answers! The questions on the actual exam will be different from the practice questions included in this book. The exam is designed to test your knowledge of a concept or objective, so use this book to learn the objectives behind the questions.
Tips for Taking the Exam
Here are some tips for taking the exam:
Give yourself plenty of time to take the exam. The official run time is 2.5 hours, so there is no need to rush things.
Read everything carefully; it can be easy to jump to conclusions about the right answer to a question and throw away points.
If you are not sure about a question, do not get stuck staring at the screen. Flag it for review and move on. You should be able to come back to it later. The exam will notify you if you cannot return.
PowerShell cmdlets used in questions can get you in a muddle, as often the cmdlets will vary by a single word or so. Look carefully at the other combinations in the other options, as this can help you rule out cmdlets that are definitely not valid. If in doubt, use the trick from the previous point and flag the question to come back to; another question or screenshot may clue you into what the right wording will be.
Unless told otherwise, assume settings are left at the default, and for any simulation questions, try not to change any settings that are not directly related to the task you have been asked to perform.
No points are deducted for getting a question wrong, so if in doubt make an educated guess. You should be able to narrow down your options by at least eliminating one or two incorrect answers.
Put your day job to one side for the exam, and do not get caught up in the real world versus the material. Sometimes you just need to give the answer that Microsoft wants even if that does not match your experience of best practices. Remember that for the exam purposes you are a fully fledged enterprise administrator juggling many workloads for a large multinational company.
Building Knowledge Chapter by Chapter
The chapters in this book are not directly lined up with the MS-700 objectives but are instead laid out in what I would argue is a more logical manner that fits better with how you would actually deploy Teams.
Each chapter starts with an introduction that includes which sections are going to be covered in the chapter, but you can also refer to the table in the “MS-700 Objectives” section later in this introduction.
The following is a breakdown of what we will be covering together in each chapter:
Chapter 1, “Introducing Teams”: This chapter covers an overview of what Teams is and the core concepts behind it and how that fits with the wider Office 365 and Microsoft 365 offerings. It will also introduce some of the core concepts you will need to understand about how Teams is configured and managed.
Chapter 2, “Getting Teams Up and Running”: This chapter covers three main areas: Skype for Business migrations, network preparation, and client deployments. This chapter helps lay the foundations of understanding how Teams interacts with Skype for Business if you have it deployed and need to migrate away from it. It covers how to best prepare your network for dealing with Teams (mostly) media traffic and how to get the Teams client out to your end users and on your devices.
Chapter 3, “Teams Core Functionality”: This chapter covers Teams bread-and-butter tasks such as different types of teams, how to manage basic policies, how to control access to your Teams, and how to manage meetings.
Chapter 4, “Advanced Teams Functionality and Management”: This chapter covers how to apply security and governance against your Teams deployment and how to make sure your data is safe, secure, and available only to the people who need it. We will also look at things such as templates and app policies.
Chapter 5, “Adding Telephony”: This chapter covers how to incorporate PSTN calling into Teams, the different ways this can be delivered, and how this functionality works.
Chapter 6, “Review Usage and Maintain Quality”: It is all very well having Teams deployed and all your users enabled and configured, but you should also be proactively looking at how they are performing. This chapter will cover some of the tools you need to monitor usage and track down issues.
