You have a server named Server1 that runs Windows Server 2012 R2.
You try to install the Microsoft .NET Framework 3.5 Features feature on Server1, but the installation fails
repeatedly.
You need to ensure that the feature can be installed on Server1.
What should you do?

A.
Install Windows Identity Foundation (WIF) 3.5.

B.
Install the Web Server (IIS) server role.

C.
Connect Server1 to the Internet.

D.
Run the Add-AppxProvisionedPackage cmdlet.

Explanation:
The files needed are no longer available on the local Hard drive. We need to connect the server to the Internet.Important to note that when starting with Windows Server 2012 R2 and Windows 8, the feature files for .NET
Framework 3.5 (which includes .NET Framework 2.0 and .NET Framework 3.0) are not available on the local
computer by default. The files have been removed. Files for features that have been removed in a Features on
Demand configuration, along with feature files for .NET Framework 3.5, are available through Windows Update.
By default, if feature files are not available on the destination server that is running Windows Server 2012 R2
Preview or Windows Server 2012 R2, the installation process searches for the missing files by connecting to
Windows Update. You can override the default behavior by configuring a Group Policy setting or specifying an
alternate source path during installation, whether you are installing by using the Add Roles and Features Wizard
GUI or a command line.