Skip Navigation Links
 

Archive - 70-695: Deploying Windows Desktops and Enterprise Applications

Sample Questions

Question: 114
Measured Skill: Implement a Lite Touch deployment (18%)
Note: This questions is based on a case study. The case study is not shown in this demo.

You need to modify the MDT settings to meet the operating system deployment requirements for the tablets.

Which file should you modify?

(To answer, select the appropriate options in the answer area.)

www.cert2brain.com

AFile to modify: Config.xsd
Folder that contains the file: Servicing
B File to modify: CustomSettings.ini
Folder that contains the file: Control
C File to modify: LTIApply.wsf
Folder that contains the file: Scripts
D File to modify: Settings.xml
Folder that contains the file: Tools

Correct answer: C

Explanation:

The case study states:

Ensure that Windows can be deployed to tablets by using the CompactOs option.

With Windows 10, the compact OS setup does not require any special images or additional partitions.  It doesn’t use a WIM file, and the compressed files are stored on the normal OS volume.  So there are no special steps needed to configure a machine for compact OS.  You just need to specify that this should be enabled.  There are different ways to do this, depending on how you are deploying (or have deployed) Windows 10.  These are covered in the following sections.

Compact OS manually

If you want to try the new compact OS capability, you can do this directly from Windows PE.  Here are the steps:

  1. Format and partition the disk as required.
  2. Apply the OS image to an NTFS partition using DISM:

    DISM.EXE /Apply-Image /ImageFile:INSTALL.WIM /Index:1 /ApplyDir:C:\ /Compact:ON

  3. Run BCDBOOT C:\WINDOWS to set up the OS to boot.
  4. Reboot.

Compact OS with MDT 2013 Update 1

With MDT 2013 Update 1, MDT moved from using ImageX.exe to apply images to instead use DISM.EXE.  That’s convenient, because it makes it easy to tweak MDT to add the /Compact:ON switch.  To do this, open up LTIApply.wsf in Notepad and find these lines and add the three highlighted ones:

' Apply the image

sCmd = " /Apply-Image /ImageFile:""" & sImagePath & """"
If sRWMPath <> "" then
    sCmd = sCmd & " /SWMFile:""" & sRWMPath & """" 
End if
If sSWMPath <> "" then
    sCmd = sCmd & " /SWMFile:""" & sSWMPath & """" 
End if
sCmd = sCmd & " /Index:" & sImageIndex & " /ApplyDir:" & sDestinationDrive
If UCase(oEnvironment.Item("OSDCompact")) = “TRUE” then
    sCmd = sCmd & " /Compact:ON"
End if

With those new lines in place, any time the “OSDCompact” variable is set to TRUE, it will add the DISM command line option to set up the compact OS while the image is being applied.  (You might want to set this variable conditionally, e.g. only on systems with 32GB or smaller hard drives.)

Compact OS with ConfigMgr

In theory, you can do something similar with ConfigMgr, replacing the built-in “Apply Operating System” step with a script that does the same thing.  But that’s quite a bit of work, for a couple of reasons:

  • The script needs to set the same variables that the built-in step does, otherwise the task sequence will fail.
  • The script can’t be used from a “Run command line” step because you can’t use an OS image package with such a step.  To work around this, you need to create a new custom step and add that to the task sequence editor via a MOF file.  (You can cheat and reuse the “Apply Operating System” step’s UI, since the script needs the same inputs anyway.  That just ends up looking rather weird.)

Fortunately, there is an easier way.  You can allow the OS to be deployed without initially configuring it for compact OS, then convert it afterwards, as part of the task sequence.  This will temporarily take up more disk space (about 3GB on a 64-bit system), but I’ll take that for the simplicity of it.

To make this work, set up a new “Run command line” step somewhere in the “State Restore” phase of an MDT-generated ConfigMgr task sequence for Windows 10.  For this step, specify the following command line:

COMPACT.EXE /CompactOS:always

This uses one of the new compact OS switches that have been added to COMPACT.EXE in Windows 10.  This will take 15-20 minutes to compact the OS files, but that’s all there is to it.

Compact OS manually, take 2

You can probably guess from the ConfigMgr section above that the exact same COMPACT.EXE command line can be used on any Windows 10 system to enable (compress) or disable (decompress) compact OS.  Feel free to try it on your system:

COMPACT.EXE /CompactOS:always

knowing you can turn it back off again with:

COMPACT.EXE /CompactOS:never

Reference: Windows 10: Reducing the disk footprint



Question: 115
Measured Skill: Prepare and deploy the application environment (20%)
Note: This questions is based on a case study. The case study is not shown in this demo.

You need to meet the Office Deployment requirement for the sales department.

What command should you run first?

(To answer, select the appropriate options in the answer area.)

www.cert2brain.com

A\\Server2\Share1\Setup.exe /admin
B \\Server2\Share1\Setup.exe /configure
C \\Server2\Share1\x64\proplus.ww\office64ww.msi /modify
D \\Server2\Share1\x86\proplus.ww\office32ww.msi /admin
E \\Server2\Share2\Setup2\Setup.exe /packager
F \\Server2\Share2\Setup2\Setup.exe /config

Correct answer: A

Explanation:

The Office Deployment Requirements section contains the following:

Office 2013 to the sales department by using a setup customization (.msp) file.

Setup.exe /admin starts the Microsoft Office Customization Tool. This tool enables administrators to create a .MSP file, which when attached to a Pro version of Office 2013 and a volume license makes an Office 2013 deployment much more appealing.

Reference: Step-By-Step: Customizing An Office 2013 Installation

Question: 116
Measured Skill: Prepare and deploy the application environment (20%)
Note: This questions is based on a case study. The case study is not shown in this demo.

You need to meet the Office deployment requirement for the marketing department.

What command should you run on the marketing department computers?

(To answer, select the appropriate options in the answer area.)

www.cert2brain.com

A\\Server2\Share1\Setup.exe /admin
B \\Server2\Share1\Setup.exe /configure
C \\Server2\Share1\x64\proplus.ww\office64ww.msi /modify
D \\Server2\Share1\x86\proplus.ww\office32ww.msi /admin
E \\Server2\Share2\Setup2\Setup.exe /packager
F \\Server2\Share2\Setup2\Setup.exe /configure

Correct answer: F

Explanation:

The Office Deployment Requirements section contains the following:

Office 2013 Click-to-Run to the marketing department by using Configuration1.xml.

The Office 365 Click-to-Run Configuration File section contains the following:

Configuration1.xml is stored in \\Server2\Share2.

Configuration1.xml was used to download and create an installation source for Click-To-Run.


To install the downloaded Office 365 ProPlus products and languages on a client computer, use configure mode. You also use configure mode to remove and update Office products and languages.

Example: setup.exe /configure installconfig.xml

Question: 117
Measured Skill: Prepare and deploy the application environment (20%)
Note: This questions is based on a case study. The case study is not shown in this demo.

You deploy Office to the marketing department computers to meet the Office deployment requirements.

Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the case study.

www.cert2brain.com

AOffice updates for the marketing department are downloaded from \\Server3\Share1.
Office shortcuts and tooltips for the marketing department are in German only.
B Office updates for the marketing department are downloaded from \\Server3\Share1.
Office shortcuts and tooltips for the marketing department are based on the Windows locale.
C Office updates for the marketing department are downloaded from the internet.
Office shortcuts and tooltips for the marketing department are in English only.
D Office updates for the marketing department are downloaded from the internet.
Office shortcuts and tooltips for the marketing department are based on the Windows locale.
E Office updates for the marketing department are not downloaded.
Office shortcuts and tooltips for the marketing department are in German only.
F Office updates for the marketing department are not downloaded.
Office shortcuts and tooltips for the marketing department are in English only.

Correct answer: C

Explanation:

The office configuration file has updates enabled but not path for update files sepcified. This means, updates are downloaded from Microsoft.

The first language defined in the language element determines the Shell UI language. The Shell UI is the language that is used to display shortcuts, right-click context menus, and tooltips. If you decide that you want to change the Shell UI language after an initial installation, you have to uninstall Office and reinstall it.

References:

Managing Updates with Office 2013 Click-to-Run

Overview of deploying languages in Office 365 ProPlus

Question: 118
Measured Skill: Implement a Lite Touch deployment (18%)
Note: This questions is based on a case study. The case study is not shown in this demo.

You need to meet the technical requirements for the default WDS boot image.

What Windows PowerShell cmdlet should you run on Server1?

(To answer, select the appropriate options in the answer area.)

www.cert2brain.com

ADisable-WdsBootImage ImageName Boot2 -DisplayOrder 5000 -Architecture x64
B Enable-WdsBootImage ImageName Boot1 -NewImageName AAA -Architecture x64
C Enable-WdsBootImage ImageName Boot3 -DisplayOrder 100 -Architecture x64
D Remove-WdsBootImage ImageName Boot4 -DisplayOrder 5000 -Architecture x64
E Set-WdsBootImage ImageName Boot2 -NewImageName AAA -Architecture x64
F Set-WdsBootImage ImageName Boot3 -DisplayOrder 100 -Architecture x64

Correct answer: F

Explanation:

The Technical Requirements states, that Boot3.wim must be configured as the default WDS boot image.

The Set-WdsBootImage cmdlet modifies information associated with a boot image in the Windows Deployment Services image store. You can use the cmdlet to change the name and description of the boot image, set the display order in the boot menu, and enable the boot image for multicast transmissions.

Specify the boot image by using the ImageName and Architecture parameters. If the image name and architecture do not uniquely identify the image, also specify the FileName parameter.

The DisplayOrder parameter specifies the order in which images appear in the boot menu on Pre-Boot Execution Environment (PXE) clients. The menu lists the boot images in ascending order, smallest number to largest number.

If two boot images have the same display order, the imported images appear in alphabetical order of file name.



 
Tags: exam, examcollection, exam simulation, exam questions, questions & answers, training course, study guide, vce, braindumps, practice test
 
 

© Copyright 2014 - 2019 by cert2brain.com