Free Microsoft Dynamics MB-820 Actual Exam Questions - Question 1 Discussion
HOTSPOT You need to log an error in telemetry when the business process defined in the custom application developed for Contoso, Ltd fails. How should you complete the code segment? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.
I’d go with options that involve creating a new Exception specifically for the business failure and then using TrackException to log it. That’s the cleanest way to capture an error in telemetry instead of just logging a string message. Also, including custom properties about the failure lets you filter and analyze these errors later. Anything that skips making a proper Exception or just logs info messages probably won’t work here. So I’m focusing on options that show throwing or creating an Exception and calling TrackException with it.
Another angle is to look for options that include creating a new Exception object with a clear message about the business process failure before passing it to TrackException. This makes sure the error logged is descriptive and specific, which helps in troubleshooting later. Also, including any relevant business context as custom properties can make the telemetry data more useful. So, choices that combine building a detailed exception and using TrackException with those details should be solid picks here.
I’d pick the choices that explicitly use the telemetry client’s TrackException method with custom properties about the business failure. That way, the error’s tied to the specific process, not just a generic error log.
I’d rule out any options that just use generic logging methods without specifying the business failure context. The right choice should show a way to capture the error within the custom app’s logic explicitly.
For this, I'd focus on options that show explicit logging of the business process failure, not just generic exceptions. Picking choices that involve custom event tracking or error messages linked to the business logic makes more sense.
I think the key here is making sure the error event is tied directly to the business logic failure, not just a generic catch block. Options that mention tracking exceptions with custom properties or event names seem better. Anything too generic might miss the context we need for proper telemetry insight. Also, using a method that explicitly logs an error or exception rather than just info or debug makes more sense for this scenario.
Not sure about the exact syntax here, but I’d skip anything with generic exception handling (trap there). Logging a specific error related to the business process seems key. Would pick options that reference telemetry directly.