nerdexam
Microsoft

70-489 · Question #19

You configure a SharePoint app to collect diagnostic information. The app must meet the following requirements: Record messages about all unrecoverable events that limit the functionality of the…

The correct answer is D. Monitorable. This question tests knowledge of SharePoint ULS trace log levels and selecting the level that satisfies specific logging requirements while minimizing performance overhead.

Implement an application lifecycle management (ALM) process for Microsoft SharePoint 2013

Question

You configure a SharePoint app to collect diagnostic information. The app must meet the following requirements:

  • Record messages about all unrecoverable events that limit the

functionality of the app, but do not stop the app.

  • Record all events that include unexpected exceptions.
  • Minimize the effects of logging on app performance.

You need to configure the application to meet the requirements. Which trace log level should you use?

Options

  • AHigh
  • BMedium
  • CUnexpected
  • DMonitorable
  • EVerbose

How the community answered

(54 responses)
  • A
    2% (1)
  • B
    4% (2)
  • C
    7% (4)
  • D
    87% (47)

Why each option

This question tests knowledge of SharePoint ULS trace log levels and selecting the level that satisfies specific logging requirements while minimizing performance overhead.

AHigh

High captures a broader set of events beyond unrecoverable and unexpected ones, recording more than required and increasing unnecessary performance overhead.

BMedium

Medium captures even more events than High, creating greater performance impact and logging far beyond what the requirements specify.

CUnexpected

Unexpected logs only unexpected exception events and does not capture unrecoverable events that limit functionality, failing to meet the first requirement.

DMonitorableCorrect

The 'Monitorable' trace level logs unrecoverable events that limit app functionality without stopping it, and because it sits above 'Unexpected' in the severity hierarchy, it also captures all unexpected exception events. It is one of the lower-verbosity levels, so it minimizes the performance impact of logging compared to High, Medium, or Verbose, satisfying all three requirements simultaneously.

EVerbose

Verbose logs all trace events at the highest verbosity, causing the greatest performance impact and capturing far more than the requirements demand.

Concept tested: SharePoint ULS trace log level severity hierarchy

Source: https://learn.microsoft.com/en-us/sharepoint/dev/general-development/uls-logging-in-sharepoint

Topics

#trace log level#diagnostic logging#ULS logging#error severity

Community Discussion

No community discussion yet for this question.

Full 70-489 Practice