Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirement, existing environment, and problem statements. If the case study has an
All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview -
Fabrikam, Inc. is an engineering company that has offices throughout Europe. The company has a main office in London and three branch offices in Amsterdam,
Berlin, and Rome.
Existing Environment -
Active Directory Environment -
The network contains two Active Directory forests named corp.fabrikam.com and rd.fabrikam.com. There are no trust relationships between the forests.
Corp.fabrikam.com is a production forest that contains identities used for internal user and computer authentication.
Rd.fabrikam.com is used by the research and development (R&D) department only.
Network Infrastructure -
Each office contains at least one domain controller from the corp.fabrikam.com domain. The main office contains all the domain controllers for the rd.fabrikam.com forest.
All the offices have a high-speed connection to the Internet.
An existing application named WebApp1 is hosted in the data center of the London office. WebApp1 is used by customers to place and track orders.
WebApp1 has a web tier that uses Microsoft Internet Information Services (IIS) and a database tier that runs Microsoft SQL Server 2016. The web tier and the database tier are deployed to virtual machines that run on Hyper-V.
The IT department currently uses a separate Hyper-V environment to test updates to WebApp1.
Fabrikam purchases all Microsoft licenses through a Microsoft Enterprise Agreement that includes Software Assurance.
Problem Statements -
The use of Web App1 is unpredictable. At peak times, users often report delays. At other times, many resources for WebApp1 are underutilized.
Requirements -
Planned Changes -
Fabrikam plans to move most of its production workloads to Azure during the next few years.
As one of its first projects, the company plans to establish a hybrid identity model, facilitating an upcoming Microsoft Office 365 deployment.
All R&D operations will remain on-premises.
Fabrikam plans to migrate the production and test instances of WebApp1 to Azure.
Technical Requirements -
Fabrikam identifies the following technical requirements:
Web site content must be easily updated from a single point.
User input must be minimized when provisioning new app instances.
Whenever possible, existing on-premises licenses must be used to reduce cost.
Users must always authenticate by using their corp.fabrikam.com UPN identity.
Any new deployments to Azure must be redundant in case an Azure region fails.
Whenever possible, solutions must be deployed to Azure by using platform as a service (PaaS).
An email distribution group named IT Support must be notified of any issues relating to the directory synchronization services.
Directory synchronization between Azure Active Directory (Azure AD) and corp.fabrikam.com must not be affected by a link failure between Azure and the on- premises network.
Database Requirements -
Fabrikam identifies the following database requirements:
Database metrics for the production instance of WebApp1, must be available for analysis so that database administrators can optimize the performance settings.
To avoid disrupting customer access, database downtime must be minimized when databases are migrated.
Database backups must be retained for a minimum of seven years to meet compliance requirements.
Security Requirements -
Fabrikam identifies the following security requirements:
Company information including policies, templates, and data must be inaccessible to anyone outside the company.
Users on the on-premises network must be able to authenticate to corp.fabrikam.com if an Internet link fails.
Administrators must be able authenticate to the Azure portal by using their corp.fabrikam.com credentials.
All administrative access to the Azure portal must be secured by using multi-factor authentication.
The testing of WebApp1 updates must not be visible to anyone outside the company.
What should you include in the identity management strategy to support the planned changes?
Introductory Info
Question
Click on the arrows to vote for the correct answer
A. B. C. D.B
Directory synchronization between Azure Active Directory (Azure AD) and corp.fabrikam.com must not be affected by a link failure between Azure and the on- premises network. (This requires domain controllers in Azure)
Users on the on-premises network must be able to authenticate to corp.fabrikam.com if an Internet link fails. (This requires domain controllers on-premises)
The planned changes include migrating the production and test instances of WebApp1 to Azure, establishing a hybrid identity model to facilitate Office 365 deployment, and keeping R&D operations on-premises. To support these changes, an identity management strategy needs to be developed.
Based on the technical requirements, the following points should be considered for the identity management strategy:
Use existing on-premises licenses to reduce cost: Fabrikam has an Enterprise Agreement that includes Software Assurance. To reduce costs, it is recommended to use existing licenses whenever possible.
Ensure users always authenticate using their corp.fabrikam.com UPN identity: To maintain consistency and ease of use, users should always authenticate with their existing UPN identity.
Support hybrid identity model: As part of the planned changes, a hybrid identity model will be established to facilitate Office 365 deployment. This requires directory synchronization between Azure AD and corp.fabrikam.com, and authentication for on-premises users even when the internet link fails.
Use multi-factor authentication for all administrative access: To ensure security, all administrative access to the Azure portal should be secured by using multi-factor authentication.
Ensure privacy and security of company information: It is essential to keep company information, policies, templates, and data inaccessible to anyone outside the company.
Based on these requirements, option B is the best choice. Deploying domain controllers for corp.fabrikam.com to virtual networks in Azure will allow Fabrikam to maintain control over the identity management while leveraging Azure's scalability and availability. This will also support the hybrid identity model and enable users to authenticate even when the internet link fails. Additionally, it will allow the use of existing on-premises licenses, and multi-factor authentication can be used for all administrative access to the Azure portal.
Option A, moving all the domain controllers from corp.fabrikam.com to virtual networks in Azure, is not necessary as it would require reconfiguring the entire Active Directory environment and may not be cost-effective.
Option C, deploying a new Azure AD tenant for the authentication of new R&D projects, is not necessary as the existing rd.fabrikam.com forest can be maintained on-premises.
Option D, deploying domain controllers for the rd.fabrikam.com forest to virtual networks in Azure, is not required as the R&D operations will remain on-premises.