Site collections must not use Alternate Access Mappings to manage URLs.
You need to build a web application that uses claims-based authentication.
What should you do first?
A.
Option A
B.
Option B
C.
Option C
D.
Option D
E.
Option E
Explanation:
Path-based site collections use Alternate Access Mappings. We must use Host-named site
collections.
For Host-named site collections we must use Windows PowerShell commands to manage URLs (SetSPSiteURL, Remove-SPSiteURL, Get-SPSiteURL).
To create a host-named site collection we use the Windows PowerShell New-SPSite cmdlet with the
-HostHeaderWebApplication parameter.
Example: New-SPSite ‘http://portal.contoso.com’ -HostHeaderWebApplication
‘http://<servername>’ -Name ‘Portal’ -Description ‘Customer root’ -OwnerAlias
‘contoso\administrator’ -language 1033 -Template ‘STS#0’
Incorrect answers:
Not A: You must use Windows PowerShell to create a host-named site collection. You cannot use the
SharePoint 2013 Central Administration web application to create a host-named site collection.
Not B: You must use Windows PowerShell to create a host-named site collection. You cannot use the
SharePoint 2013 Central Administration web application to create a host-named site collection.
Not C: We must use HostHeaderWebApplication parameter.
Not E: We must use the New-SPSite command, not the New-SPWebApplication command.
Host-named site collection architecture and deployment (SharePoint 2013)
https://technet.microsoft.com/en-us/library/cc424952.aspx#section1b
Great, link provides additional information
But this doesn’t use Claims, any application created in PowerShell uses classic mode unless stated. Which D does not state Claims