Tracing in .NET CASENET Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which statement correctly distinguishes tracing from logging in .NET?

   • ATracing is only available in debug builds, while logging is available in release builds.
   • BTracing is a high-level abstraction for application monitoring, while logging is a low-level API for debug output.
   • CTracing is primarily used to record business transactions, while logging is used to record technical diagnostics.
   • DTracing provides a detailed view of the application's execution path, while logging records events and errors for later analysis.
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A .NET Core application uses DiagnosticSource to emit events for a long-running background job. The team wants to trace the job's progress and correlate it with the request that initiated it. The job runs in a separate Task and may outlive the original request's Activity. What is the best way to maintain correlation?

   • ACapture the Activity ID at the start of the job and manually add it to every trace message.
   • BDisable tracing for background jobs to avoid complexity.
   • CStart a new Activity for the background job and set its ParentId to the original request's Activity ID.
   • DUse the original Activity instance directly in the background task.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which of the following is a best practice for tracing in .NET?

   • AAvoid including sensitive data such as passwords, credit card numbers, or personal information in trace messages.
   • BAlways trace at the most verbose level in production to ensure no diagnostic information is missed.
   • CUse tracing only for error messages and avoid tracing successful operations.
   • DWrite trace messages to the same file as application logs to simplify management.
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   How do you attach a trace listener to a TraceSource in .NET?

   • ABy adding the listener to the TraceSource.Listeners collection.
   • BBy calling the TraceSource.AddListener method.
   • CBy registering the listener in the application's startup code using Trace.RegisterListener.
   • DBy setting the TraceSource.Output property to the listener.
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   What is a recommended practice for structuring trace messages?

   • AInclude the full stack trace for every message, even for informational messages.
   • BUse a consistent format that includes a timestamp, severity level, and relevant context such as operation ID.
   • CKeep trace messages as short as possible, using only a single word to minimize overhead.
   • DUse different formats for each component to avoid confusion.
   Reveal Solution Discussion Select an answer first