Pass Your Microsoft Azure AZ-140 Exam Easy!

Microsoft AZ-140 Configuring and Operating Microsoft Azure Virtual Desktop exam dumps vce, practice test questions, study guide & video training course to study and pass quickly and easily. Microsoft AZ-140 Configuring and Operating Microsoft Azure Virtual Desktop exam dumps & practice test questions and answers. You need avanset vce exam simulator in order to study the Microsoft Azure AZ-140 certification exam dumps & Microsoft Azure AZ-140 practice test questions in vce format.

Azure Virtual Desktop Overview

5. Azure Virtual Desktop Environment

Once you go to the Azure Portal and start making the Windows Virtual Desktop environment, you will notice three main components in the WVD environment. These are the host pools, the app groups, and the workspaces. In this lecture, I will just give you a briefing on each one, and once we start the deployment, you will see them in action. So, what is the host pool? It is a collection of Azure virtual machines that register with Windows Virtual Desktop as session hosts. So basically, the host pools are the compute power where the application will eventually be running. It's a collection of virtual machines. This is the host pool. All session host virtual machines and the host pool should be sourced from the same image, or "golden image," as we call it, for a consistent user experience. So once you want to create a housepool, you will need to have an image. It is either one from the Azure Marketplace, a preconfigured one, or a customised one you make. A host pool can be one of two types. personal, where each session host is assigned to only one user, or pooled session hosts, where session hosts can accept connections from any user authorised to an application group within the host pool. It's important to note that you can set additional properties on the host pool to change its loadbalancing behavior, how many sessions each session host can take, and what the user can do to the session hosts in the host pool while signed into the Windows Virtual Desktop sessions. All of that you can control by using the host pools. The second component is called app groups. So what is the App Group? I want you to think of it as a logical grouping of applications installed on the session hosts on the host port. So we have created the VMs in the first component, and now we have a logical grubbing of the applications we have installed there. We have installed it on the virtual machines. We put them in a logical grouping, and we give it a name. An app group can be one of two types: remote app and desktop. In the remote app group, you can actually give users access to the remote apps you individually selected and published to the application group. For example, you can assign them some of the office applications only or have a line of business application for your accountants, for example. So you can only have a group of those applications and not the full desktop experience. You can select applications and give access to those applications to your users. The other type is desktop, where users access the full desktop and have the full desktop experience. By default, a desktop application group is actually created in an automated fashion whenever you create a host pool. Whenever you create the VMs to be used, there is an application group for desktop that will be created in an automated fashion. You can disable it after, but it's going to be created at first. You can't create another desktop application group in the host pool. While a desktop application group already exists to publish the remote applications, you must create a remote application app group. It's not created by default. You have to create it and assign applications to it, and then, to assign users, you can publish resources to them by assigning them to the application groups. So once you select the applications and give them an application group and a name, you must assign who will have access to these resources within this application group. So this is the application group again. It's a collection of the things that you need the users to have access to. and these will be installed on the virtual machines of the session host. Now, moving on to the third component—and this one is called workspace— So what is a workspace? It's a logical grooming, but remember that the first component was creating the horsepower, the compute power, where the applications will be installed this time around in Windows Virtual Desktop. The second one, which is the application group, was a grouping—a logical grouping of applications that you want to give for a specific scenario. And the work space is a grouping of these application groups. Let's assume the following. You want to give a team and the company access to the full desktop experience and also to some of the applications if they want to just go and access the applications directly. So you have two application groups, one for the desktop and one for the applications. You simply group these two application groups in one workspace, which is the workspace that the user in that specific team will have access to. Each Windows Virtual Desktop Application Group must be associated with a workspace for users to see the remote apps and desktops published to them. And this is the third component in the Windows Virtual Desktop Environment. Once we start with the project, we will discuss further the deployment options, and we will create and manipulate the components that you can see. Now, before you

6. Windows 10 Enterprise Multi-Session

Windows ten enterprise multi-session This is one of the most important features of the Windows Virtual Desktop and Azure, and it is actually only available for the Windows Virtual Desktop value. So what is the Windows Ten Enterprise? Multisesian, also known as WindowsTen Enterprise for virtual desktops, It is a new remote desktop session host that allows multiple concurrent interactive sessions. In other words, more than one user can connect to This wonder is Ten, which is installed on one virtual machine. More than one user, one virtual machine Each user will have his own isolated experience, as if the virtual machine is only for him or her, and they can actually do their work on the same session host or virtual machine. Previously. only Windows Server, not Windows Ten. Windows Server could do this. This new feature in Windows 10 provides users with a familiar Windows experience while benefiting from the cost advantage of multiple installations on the same machine. And this is why it is so important. I wanted to answer some of the most common questions in this lecture that you may have in your mind now that you know what the Windows Ten Enterprise multisystem is. One of the main questions is: Can I run Windows 10 Enterprise multi-session on premises? Windows Ten Enterprise Multisession cannot run in on-premises production environments because it has been made and optimised for the Windows Virtual Desktop Service for Azure only. Another question might be, "How many users can I run concurrently?" On these Windows Ten Enterprise Multi sessions, they can also have interactive sessions. How many users? The answer to how many user interactive sessions can be active at the same time depends on the system hardware resources that you assign to the virtual machine. For example, the number of virtual CPUs, the memory disk, and the GPU as well as how your users use their applications while signed into a session and how heavy your system workload is All of these are factored in to determine the number of users that can use the same machine at the same time. But you have no hard limit. The limitation is actually only in the hardware of the VM you have. So in the coming lectures, we will have a scenario and a discussion about the users, the nature of the users, and the recommended size to be used. We will discuss this in the deployment section. The third and final question, which is one of the common questions I get asked a lot, is how do I customise the Windows Ten Enterprise multisession image for my organization? So now you know that there is something called Windows Ten Enterprise Multi-Session where you can have many users choose the same session, which will save costs for the company you are working for. So, if I want to install a line of business application, the applications of my company, in that image and use it as a session host for the WVD. How can I customise it? The answer is you can go to the Azure Portal, start a virtual machine, or create a virtual machine in Azure with a Windows Ten Enterprise Multi-Session Image. So you select this image, which is a preconfigured image in the Azure Marketplace, and you create a virtual machine. And then you access the virtual machine and start customising it by installing the line of business applications you have. Once you are done, you do the assessment prep to generalise the virtual machine, and then you create an image so you can use it when you want to create the host pool. This process and many more details will be discussed and covered in this course. How to customise the image, as well as how to use the Windows Ten Enterprise Multisition for your custom image, will be thoroughly discussed and demonstrated throughout the course. So this is it. I just wanted to make sure you are familiar with this because it's one of the greatest and most unique features of the Azure WVD.

Plan an Azure Virtual Desktop Architecture

1. Prerequisites and Deployment Components

What are the prerequisites for the WVD and the deployment components? We have these general prerequisites and components, and I will start with the one to lift the Azure subscription. Obviously, you will need an Azure subscription to deploy the virtual machine's network resources and all the items you typically need to spin up a virtual machine. Something else you need to be aware of is that your subscription needs to be registered with the Microsoft Desktop Virtualization Resource Provider. I will leave a link in the Resources section ofthis lecture so you can take a look how tocheck if this is actually registered with your subscription andif not, how to do the registration. In most cases, it is already registered and you do not need to do anything. The second one is the Azure Active Directory. You will need the Azure Active Directory to synchronise with your identity provider for the WVD so you can have the users and their passwords. And for the authentication, you can create groups, and you can use cool features like multifactor authentication and conditional access. You will also need to determine your deployment strategy, and for that we have many topics, for example, the identity strategy, how you are going to use identity, and who's going to provide the authorization and authentication for compute. So we have multiple strategies for the compute and options, and the same applies for the user's profiles. We will discuss each one of them individually in the next lectures. Also, all the Azure resources must be in one region, and by that I mean the image that you will use to spin up the session hosts, the virtual machines, the virtual network, and the storage. This will give you actually a more performance WVDsystem and will avoid latency or any issues withthe users to give them seamless experience. The final step is to ensure you have the necessary credentials to perform the Azure Ad synchronisation and the Ad Domain Join process. So for that, you will need to specify an administrator account so the provisioning process can join the virtual machines of the host pools to the domain that you have for the company. This account that you will use must be assigned the Active Directory domain administrator role. Normally, for the synchronisation with the Azure Active Directory, a global admin account can do everything, and you have more granular roles that you can use in the Azure Active Directory as well for all of the processes. Now, something else to mention is that the Azure VMs that you will create for the Windows Virtual Desktop must have a standard domain joint or a hybrid ad joint. And this is why we need that user with the Domain Admin role. And also, the Azure VMs that you will create must be running one of the supported operating system images that you can see on the slide. The Windows Virtual Desktop supports these images with the 64-bit architecture, not the 32. And for Windows 10 enterprise multi-session and single-session, the version must be something to keep in mind as well. Windows Virtual Desktop doesn't support the X86 architecture or 32 bits. Furthermore, no VHD or VHDX-based profile solutions hosted on managed Azure storage are supported by the Windows 7 version. Do you accept size limitations? So these are the things I wanted to list for you for the supported OS images for the WVT.

2. Identity Deployment Options

Azure Active Directory is used for identities and access management in Windows Virtual Desktop. This includes access to remote sessions, administration elements, and user provisions. Link WVD uses Azure ads to authenticate any operation that interacts with services running in Azure as well as for the apps and websites users use. To see what resources are available in this lecture, we will discuss identity deployment options. Two of these options are considered to be cloud-only, and one is hybrid. So let's see the first option. For the first option, you can deploy a domain controller into a hosted Windows Server virtual machine running on Azure. The domain controller runs stand-alone on a virtual network or connects with your on-premises directory service. You manage the VM yourself, so it is your responsibility, and it needs to be connected to the same virtual network your WVD session hosts will be connected to. So it's a virtual machine on Azure. You have the domain controller running on that virtual machine, and you make sure it is connected to the virtual network where the WVD session hosts will be. This is the first option. The second option is to provision Azure Active Directory Domain Services, which is a service in Azure. You don't have to maintain any domain controller VMs. Unlike the first option, you will need to connect the Azure Active Directory Domain Services service to the same virtual network as your Virtual Desktop environment. You can use Azure AD with or without a local Active Directory. It can stand alone. So these are the two cloud-only options. Let's discuss some of the pros and cons of each of them before we move on to the hybrid option. The benefits of the first option, which is deploying a domain controller and hosting a Windows Server VM in Azure, include the ability to sync with an on-premises data center. If a VPN or express route connection is configured, you can have it, for example, as a secondary domain controller as well. Also, one of the perks is that all familiar Active Directory group policies can be used, unlike the Azure Active Directory Domain Services, which is the other option. Some of the cons of the first option are that it adds additional management of a virtual machine and Active Directory in Azure. Some of the pros for the second option are that it is great for test or isolated environments that do not need connectivity to on-premises resources, and the Azure LDAP will be your leading source for identities. The cons are that the ads will always be running, resulting in a fixed charge per month. Now, what about the third option, which is the hybrid option? The third option is to connect your on-premises network to the Azure network and establish a connection between the data centre and Azure. So basically, establish a connection so you can use the on-premises domain controller. To ensure that the domain controllers you operate are securely available to the Windows virtual list of VMs running in Azure, you will need to use a VBN connection or Azure Express route. The pros of the setup are that no ActiveDirectory, Domain Services, or Domain Controllers are required in Azure; you will use the ones on premises, and the cons are obviously the latency concerns. Latency could be increased by adding delays during user authentication for virtual machines. This also assumes you have an on-premises environment, which is not suitable for cloud-only tests. For our project demonstration, I will go with the recommended option from Microsoft, which is the first option. I will deploy a domain controller in a hosted Windows Server virtual machine running in Azure, and I will make sure I deploy that VM in the same virtual network where I will deploy the host pools so we have the connection set up and ready. This is also considered to be the cheapest solution while being the most efficient as well.

3. Compute Deployment Options

The compute deployment decision is simpler. You have two deployment options. The first one is called personal, and the second one is pooled. For the personal one, it is ideal for single-session users with heavy performance requirements. So the relationship is one to one.One user will actually have one virtual machine. You will need to choose the right virtual machine to run robust business applications like Cat, SAP, and others. It supports the always-on experience and single-state retention. This is a great option for performance and heavy requirements. As for the second option, that is called bold. It is ideal for multisession users and certain single sessions with light to medium workloads with basic business requirements. You will need to choose the right VM to run most business applications. In the pooled option, more than one user will share the same virtual machine. The pooled option is a more cost-effective option. You can save money by running more than one user on one virtual machine, while the personal option is more performance oriented.Option bye.

Go to testing centre with ease on our mind when you use Microsoft Azure AZ-140 vce exam dumps, practice test questions and answers. Microsoft AZ-140 Configuring and Operating Microsoft Azure Virtual Desktop certification practice test questions and answers, study guide, exam dumps and video training course in vce format to help you study with ease. Prepare with confidence and study using Microsoft Azure AZ-140 exam dumps & practice test questions and answers vce from ExamCollection.