Microsoft 70-412日本語 valid exam dumps : Configuring Advanced Windows Server 2012 Services (70-412日本語版)

• A. Option A
• B. Option C
• C. Option B
• D. Option D

• A. Option A
• B. Option C
• C. Option B
• D. Option D

• A. Option A
• B. Option C
• C. Option B
• D. Option D

Explanation: Only visible for ValidDumps members. You can sign-up / login (it's free).

Explanation

Box 1: Server1
For all types of application that you can publish using AD FS preauthentication, you must add a AD FS relying party trust to the Federation Service.
Use Server1 as it has AD FS.
Box 2: Server2
When publishing applications that use Integrated Windows authentication, the Web Application Proxy server uses Kerberos constrained delegation to authenticate users to the published application.
Box 3: Server2
To publish a claims-based application
1. On the Web Application Proxy server, in the Remote Access Management console, in the Navigation pane, click Web Application Proxy, and then in the Tasks pane, click Publish.
2. On the Publish New Application Wizard, on the Welcome page, click Next.
Etc.
Box 4: Server2
Configure CAs and certificates (see c below)
Web Application Proxy servers require the following certificates in the certificate store on each Web Application Proxy server:
a) A certificate whose subject covers the federation service name. If you want to use Workplace Join, the certificate must also contain the following subject alternative names (SANs): <federation service name>.<domain> and enterpriseregistration.<domain>.
b) A wildcard certificate, a subject alternative name (SAN) certificate, several SAN certificates, or several certificates whose subjects cover each web application.
c) A copy of the certificate issued to external servers when using client certificate preauthentication.
Reference: Install and Configure the Web Application Proxy Server; Planning to Publish Applications Using Web Application Proxy; Publish Applications using AD FS Preauthentication

Explanation

SO...the first part of this answer is:
1. Create a new site object named Branch2
*When you create the new site Branch2 you will be prompted to associate it with a site link...right now we only have one site link (Main-Branch1). Hit Finish
2. Remove Branch2 site from the Main-Branch1 Site Link
*In order to move a site into a new site link, you must first remove them from their previous site link....In this case Branch2 was put in Main-Branch1 when we create the new site because we didn't have another site link to associate the new site with at the time we created it.
3. Create a new site link object named Main-Branch2
*When you create the site link object you will be asked to place the appropriate sites in this link...choose Main and Branch 2 Because we are using Interstice topology replication, ISTG (similar to KCC with Intrasite) will build a logical transitive connection path between all site links because site link bridge is enabled by default and is a Microsoft best practice to leave this default.
By default a site link has a default cost of 100 so the Main-Branch1 site cost 100. Since we do not have a site link established from Branch2 - Branch1, ISTG will create a logical patch that travels along the Main-Branch2 site link (cost 100) and through Main-Branch1 site link(cost 100) to establish replication connection in the event the least cost path goes down. Since the logical path =200, Branch2 will only replicate with Branch1 if the site link to the Main Site goes down.