Exam Ref 70-331: Core Solutions of Microsoft SharePoint Server 2013

Errata for Exam Ref 70-331: Core Solutions of Microsoft SharePoint Server 2013




The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed, PDF, Other Digital Version
Page 1
Entire book

Hi Where is the 15% off exam offer that is supposed to come with this book? I am unable to locate it. I have a Kindle version of the book. Thanks Michael

Note from the Author or Editor:
The exam 15% off voucher is not in the electronic copy of this book - to request a voucher, please email mspinput@microsoft.com.

Anonymous  Aug 10, 2013 
Printed, PDF
Page 10
Second bullet

The word "site column" is used when describing the inheritance of the "content type" CT2.

Note from the Author or Editor:
Second bullet should read "A content type created at a subsite level (CT2) is available to that site and its child sites."

Jason Warren  Aug 01, 2013 
Printed, PDF
Page 24
5th paragraph

The sentence "After the mapping was created, a full search had to complete..." is missing the word "crawl' after "search." It should read "After the mapping was created, a full search crawl had to complete..."

Note from the Author or Editor:
Verified - this should read "After the mapping was created, a full search crawl had to complete before the managed properties could be used in a custom search results page (rendered via XSLT)."

Jason Warren  Aug 01, 2013 
Printed, PDF
Page 52
4th bullet

"web" is misspelled as "wen" - "This is a threshold limit of 300 MB per web application"

Note from the Author or Editor:
Bullet four of the "Web application limits" topic should read: * Solution cache size - This is a threshold limit of 300MB per web application.

Jason Warren  Aug 12, 2013 
Safari Books Online
52
Answer of question 3 of chapter 1.2 . Answer is not D

Its a book of the exam ref for sharepoint 2013 core solutions. As stated in the book om page 52 "web server and application limits" "Application pools : this is a supported limit of 10 per webserver; this number is a guideline that is heavenly influenced by the following..."

Note from the Author or Editor:
p.52, in the Web server and application limits section: Bullet One should read: * Application pools - This is a threshold limit of 10 per web server; this number is a guideline that is heavily influenced by the following: The answer for question 3 of Objective Review 1.2 is "D. There is a threshold limit of 10 application pools per web server in a SharePoint farm."

Ddpham  Aug 27, 2013 
Printed, PDF, Safari Books Online
Page 52
Application pools in "web server and application limits"

Its a book of the exam ref for sharepoint 2013 core solutions. As stated in the book om page 52 "web server and application limits" "Application pools : this is a supported limit of 10 per webserver; this number is a guideline that is heavenly influenced by the following..." It ahould be a thres hold and not supported, according to the msdn library. Please informe which data is accurate? I am believing the data from the msdn is leading but please correct me of im wrong. The answer of the question of 1.2 question 3 on page 96 also states ita a threshold. Greets Ddp

Note from the Author or Editor:
p.52, in the Web server and application limits section: Bullet One should read: * Application pools - This is a threshold limit of 10 per web server; this number is a guideline that is heavily influenced by the following: The answer for question 3 of Objective Review 1.2 is "D. There is a threshold limit of 10 application pools per web server in a SharePoint farm."

Ddpham  Aug 27, 2013 
Printed
Page 55
2nd bullet

The default maximum file size (maximum upload size) in SharePoint 2013 has increased from 50 MB to 250 MB

Note from the Author or Editor:
The initial number was correct, but the TechNet documentation changed the maximum file size from 50MB to 250MB in their latest documentation. p. 55, List and library limits, bullet 2 should now read: * File size - This is a boundary limit of 2GB; the default maximum file size is 250 MB but can be increased to 2GB. Increasing file size to 2 GB can have a negative effect on farm performance.

Jason Warren  Aug 13, 2013 
Printed, PDF
Page 62
4. Create the example web application:

We already defined $Provider in step 3, so we should use it by providing it to the switch -AuthenticationProvider So the whole command gonna be: New-SPWebApplication -ApplicationPool $AP -ApplicationPoolAccount $APAcct -Name $WA -Port 80 -AuthenticationProvider $Provider -DatabaseName $ContentDB Also, no need to to put A. as it's just one step ;)

Note from the Author or Editor:
p. 62, mid-page, item #4. Create the example web application. As per errata submitted, PowerShell should read "New-SPWebApplication -ApplicationPool $AP -ApplicationPoolAccount $APAcct -Name $WA -Port 80 -AuthenticationProvider $Provider -DatabaseName $ContentDB"

Ibrahem Khalil  Nov 27, 2013 
PDF
Page 69
Pre Last Paragraph

Additional configuration for the **throttling** rules can be administered using the **Get-/Set-SPThrottlingRule** PowerShell cmdlet. Should be (as we are talking now about Routing Rulse): Additional configuration for the **routing** rules can be administered using the **Get-/Set-SPRoutingRule** PowerShell cmdlet.

Note from the Author or Editor:
On p. 69, the second to last paragraph should read "Routing rules can be enabled or disabled using the -RoutingEnabled parameter of the Set-SPRequestManagementSettings cmdlet. Additional Configuration for the routing rules can be administered using the Get-/Set-SPThrottlingRule PowerShell cmdlet."

Ibrahem Khalil  Nov 27, 2013 
Printed, PDF
Page 75
Last Bullet

The bullet of "Microsoft .NET Framework version 4.5" Should be moved to right, it should not be under the bullet of "Hotfix: ASP.NET (SharePoint) race condition in .NET 4.5 RTM"

Note from the Author or Editor:
p. 75, last bullet under "Software requirements for database server installations in a farm" should not be a sub-bullet under "Hotfix: ASP.NET...". It should read: * Microsoft .NET Framework version 4.5 (positioned to the leftmost bullet)

Ibrahem Khalil  Nov 27, 2013 
PDF
Page 75
Last Bullet

The bullet of "Microsoft .NET Framework version 4.5" Should be moved to right, it should not be under the bullet of "Hotfix: ASP.NET (SharePoint) race condition in .NET 4.5 RTM"

Note from the Author or Editor:
p. 75, last bullet under "Software requirements for database server installations in a farm" should not be a sub-bullet under "Hotfix: ASP.NET...". It should read: * Microsoft .NET Framework version 4.5 (positioned to the leftmost bullet)

Ibrahem Khalil  Nov 27, 2013 
Printed
Page 77
2nd Paragraph

Section entitled 'Planning server Load Balancing' contains the following statement : "Any load balancer intended for use with Sharepoint requires the capability to setup persistent/sticky/affinity sessions." This is incorrect - sticky sessions are no longer required with Sharepoint 2013 due to the introduction of the Distributed cache service as documented here : http://technet.microsoft.com/en-us/library/jj219758.aspx "By storing the login tokens in the Distributed Cache Service in SharePoint 2013, the configuration of affinity in your load balancing solution is no longer required. There are also scale-out benefits and less memory utilization in the web front-ends because of a dedicated cache service."

Note from the Author or Editor:
On p. 77 in the Planning server load balancing section, remove paragraph 3, which begins with "Any load balancer intended..." Replace with an "IMPORTANT" note - "In prior versions of SharePoint, it was recommended that sticky sessions be configured when using a load balancing technology. SharePoint 2013 includes functionality provided by the Distributed Cache Service for caching the FedAuth token. This eliminates the need for sticky sessions (load balancing affinity) with the associated load balancing service. See http://social.technet.microsoft.com/wiki/contents/articles/20348.sharepoint-2013-appfabric-and-distributed-cache-service.aspx for details.

Paul Lynch  Sep 16, 2013 
PDF
Page 98
D.

Yes, D is the correct answer indeed. But question 3., is about "Sharing" not "Quotas". So Quotas should be replaced with sharing

Note from the Author or Editor:
p. 98, answer 3.D should read: "D. Sharing is part of the configuration for site collections."

Ibrahem Khalil  Nov 28, 2013 
PDF
Page 180
Answer of Question 4

Anonymous authentication can be configured also at the site collection level although it must be configured first at the Zone level. So I think that also C is a correct answer as well.

Note from the Author or Editor:
p. 98, answer 3.D should read: "D. Sharing is part of the configuration for site collections."

Ibrahem Khalil  Nov 28, 2013 
Printed, PDF
Page 218
SPD settings in Central Administration

In all the bullets that explain the check boxes of SPD settings, You are sating that allowing "checking" the option will "disallow" or "precludes" an action. That is untrue, checking the option will allow the action.

Note from the Author or Editor:
On p. 218, in the "Allow SharePoint Designer To Be Used In This Web Application", the text should read "Selecting this setting allows the use of SPD with this web application." On p. 218, in the "Allow Site Collection Administrators To Detach Pages From The Site Template", the last sentence of this bullet should read "Selecting this setting allows the pages to be detached from the Site Template." On p. 219, in the "Allow Site Collection Administrators To Customize Master Pages And Layout Pages", the last sentence of this bullet should read "Selecting this setting allows the customization of these page types." On p. 219, in the "Allow Site Collection Administrators To See The URL Structure Of Their Web Site", the text should read "Selecting this setting allows designers to see and interact with the internal structure of their site."

Ibrahem Khalil  Nov 30, 2013 
Printed
Page 293
Answer 3 B

Answer detailed makes no sense to question being asked

Note from the Author or Editor:
On p. 293, Answer 3. (B) should read: "Incorrect: There is no such cmdlet"

Paul Grimley  Sep 05, 2013 
PDF
Page 293
The answer of question 2

None of the answers is correct. This cmdlet that is used to create a new proxy group is "New-SPServiceApplicationProxyGroup "

Note from the Author or Editor:
On p.232, question #2, answer A should read: A. New-SPServiceApplicationProxyGroup

Ibrahem Khalil  Nov 30, 2013 
PDF
Page 295
Answer of question 3

All occurrences of "published" must be replaced with "Unpublished" as the question is about "Unpublished"

Note from the Author or Editor:
On p. 295, the answer key for Question 3 should read: A. Incorrect: The term "Uncustomized" does not describe the status of an unpublished content type. B. Incorrect: The term "Customized" does not describe the status of an unpublished content type. C. Incorrect: The term "Sealed" does not describe the status of an unpublished content type. D. Correct: The term "Unsealed" describes the status of a published content type.

Ibrahem Khalil  Nov 30, 2013 
Printed
Page 309
Germany

Table 4-2 List Unique Permissions Threshold is not 5.000 unique permissions. It is 50.000.

Note from the Author or Editor:
Per http://technet.microsoft.com/en-us/library/cc262787, the Security scope threshold is indeed 50,000 unique scopes, although the recommendation is 5,000 unique scopes. In Table 4-2, change the List Unique Permissions Threshold from 5,000 unique permissions to 50,000 - this is the correct threshold value.

Danny Davis  Sep 30, 2013 
Printed, PDF
Page 364
Figure 4-90

The figure is incorrect. It is the same as 4-89

Note from the Author or Editor:
The 4-90 Figure is not correct, what should be shown is the Query Transform section of the Add Result Source - The Query Transform should read "{searchTerms} fileextension = one"

Anonymous  Oct 03, 2013 
Printed
Page 379
2nd paragraph

The first bullet of the Objective summary talks about "result scope", but it should be "result source"

Note from the Author or Editor:
The first bullet of the Objective summary on p. 379 should read, "Search scopes are deprecated in SharePoint 2013, having been replaced by result sources."

Daniyar Satkhanov  Aug 07, 2013 
Printed, PDF
Page 399
Answers 2.

Answer to the Question n 2 for Objective 4.4: At which of the following levels can you configure query results: A. Search service application B. Site or site collection C. Web application D. All of the above states correct answers B and C and it must be A and B. Query rules are available at search application level in Central Admin and not available at Web application. Refer to http://blogs.technet.com/b/mspfe/archive/2013/02/01/how-query-rules-and-result-sources-can-be-used-to-customize-search-results.aspx

Note from the Author or Editor:
The Answer to Objective 4.4 Review, Question 2 should read: 2. Correct answers: A, B A. Correct: Query rules can be configured at the search service application level B. Correct: Query rules can be configured at the site or site collection level C: Incorrect: Query rules cannot be configured at the web application level D. Incorrect: Only answers A and B are correct

Daniyar Satkhanov  Aug 05, 2013 
Printed, PDF
Page 399
3rd paragraph

The Answer provided for question 3 is wrong, as well as it contains a typo: "Display folder" must be "display template".

Note from the Author or Editor:
The answer for Objective 4.4, Item #3 should read: 3. Correct answer: B A. Incorrect: This folder does not house the display templates for result types. B. The Search folder houses the display templates for result types. C. Incorrect: This folder does not house the display templates for result types. D. Incorrect: This folder does not house the display templates for result types.

Daniyar Satkhanov  Aug 05, 2013 
Printed, PDF
Page 424
First paragrah in "Monitoring content databases" section

The sentence "Central Administration does not provide a method to farm administrators for reviewing the size of either content databases or site collections." is partially incorrect. There is a way in Central Administration to see how much space a certain site collection is using. That is done by going to "Application Management" > "Configure quotas and locks" and looking at the "Current storage used" under the "Site Quota Information" section.

Note from the Author or Editor:
Replace the first paragraph of Monitoring Content Databases with: "SharePoint 2013 Central Administration is limited in its ability to monitor Content Databases. The size of individual site collections can be reviewed from the "Configure Quotas and Locks" section of Application Management. To review this information, open Application Management > Configure quotas and locks and then look at Current Storage used (within the Site Quota Information section). Unfortunately, there is not a way to review the sizes of multiple site collections or their respective content databases from within Central Administration. Windows PowerShell, on the other hand, provides a couple of different cmdlets for reviewing SharePoint databases: Get-SPDatabase and Get-SPContentDatabase."

Vili Bogdan  Jul 05, 2013