Feedback
Home
You may like this!
26.
You can make an individual site collection read-only with all except which of the following?
  • A.
    Central Administration
  • B.
    The PowerShell command Set-SPSite
  • C.
    SQL Server
  • D.
    The stsadm command setsitelock
  • Answer & Explanation
  • Report
Answer : [C]
Explanation :
  • A. Incorrect: You can use Central Administration to set an individual site collection to read-only in the Quotas and Locks section.
  • B. Incorrect: You can use the PowerShell command Set-SPSite to set a site collection to read-only, using the -LockState “ReadOnly” parameter.
  • C. Correct: SQL Server can’t be used to set an individual site collection as read-only. It can be used only to set an entire content database as read-only.
  • D. Incorrect: The stsadm command setsitelock can still be used, even though it is deprecated.
Report
Name Email  
27.
The PowerShell command Test-SPSite can be used to do which of the following functions?
  • A.
    Test a site collection for possible upgrade issues.
  • B.
    Test a site collection for possible upgrade issues and fix the issues if found.
  • C.
    Test an individual subsite for possible upgrade issues
  • D.
    All of the above
  • Answer & Explanation
  • Report
Answer : [A]
Explanation :
  • A. Correct: You can use the PowerShell command Test-SPSite to test site collections for possible issues to the upgrade process.
  • B. Incorrect: You can’t use the PowerShell command Test-SPSite to repair issues, but you can use the PowerShell command Repair-SPSite to repair some of the issues (such as setting customized sites back to their defaults).
  • C. Incorrect: You can’t use the PowerShell command Test-SPSite to target an individual subsite. It can target only a site collection.
  • D. Incorrect: Because the only correct answer was A, D has to be incorrect.
Report
Name Email  
28.
By using the pre-upgrade health check on a site collection, you have discovered that you have a content type with the same name. What should you do to resolve this issue?
  • A.
    Delete the pre-existing content type
  • B.
    Rename the pre-existing content type.
  • C.
    Upgrade to the SharePoint 2013 user experience and then delete the newer content type.
  • D.
    Nothing additional is required. SharePoint 2013 will fix it for you.
  • Answer & Explanation
  • Report
Answer : [B]
Explanation :
  • A. Incorrect: Deleting the content type will cause issues if it’s used by a list, library, or the parent of another content type.
  • B. Correct: Renaming the site content type allows you to keep the functionality of the pre-existing content type.
  • C. Incorrect: Trying to upgrade the site collection to the SharePoint 2013 user experience will cause an error.
  • D. Incorrect: This type of error needs to be resolved manually.
Report
Name Email  
29.
By default, SharePoint 2013 allows you to create what kind of site collections within an upgraded content database?
  • A.
    Only SharePoint 2013 experience site collections.
  • B.
    Only SharePoint 2010 experience site collections, until all site collections are upgraded to the SharePoint 2013 experience.
  • C.
    Both SharePoint 2013 and SharePoint 2010 experience site collections can be created.
  • D.
    No site collections can be created in an upgraded site collection
  • Answer & Explanation
  • Report
Answer : [C]
Explanation :
  • A. Incorrect: Unless the farm administrator has turned off the ability to create Share- Point 2010 site collections, they can still be created within an upgraded (or new) content database.
  • B. Incorrect: SharePoint 2013 site collections can be created in an upgraded content database unless explicitly turned off by the farm administrator.
  • C. Correct: Both the SharePoint 2010 user experience and the SharePoint 2013 user experience are supported in SharePoint 2013 by default.
  • D. Incorrect: Site collection can be created in upgraded content databases in the same way as they are in new content databases.
Report
Name Email  
30.
You’ve just finished attaching the backup of a SharePoint 2010 content database to a SharePoint 2013 web application and verified that it functions on the new farm and that the health checks are clean. You now want to upgrade to the SharePoint 2013 experience using PowerShell. Which command-line syntax can you use for your site collection http://contoso?
  • A.
    Upgrade-SPSite http://contoso.
  • B.
    Upgrade-SPSite http://contoso -VersionUpgrade.
  • C.
    Upgrade-SPSite http://contoso -VersionUpgrade -QueueOnly
  • D.
    Nothing is needed. When the health check runs clean, it will automatically upgrade to the SharePoint 2013 experience.
  • Answer & Explanation
  • Report
Answer : [B][C]
Explanation :
  • A. Incorrect: By default, the Upgrade-SPSite command does a content-to-content upgrade and not a version upgrade.
  • B. Correct: This command upgrades the site collection to the SharePoint 2013 experience because it has the VersionUpgrade parameter specified.
  • C. Correct: This command upgrades the site collection to the SharePoint 2013 experience because it has the VersionUpgrade parameter specified. The additional parameter QueueOnly means it will go in the queue rather than be run immediately.
  • D. Incorrect: The process of upgrading to the full SharePoint 2013 experience is a two-stage process. The upgrade is a manually started process that must be initiated either by the farm administrator or a site collection administrator.
Report
Name Email  
 
  © 2024 infibee.com. All Rights Reserved.   Copyright | Privacy Policy | Sitemap  
Contact us on : info@infibee.com  
 
 
Share   Facebook   Twitter   Google +   Digg