What are two types of Guidewire Profiler?

The Guidewire Profiler is the primary tool used by developers to diagnose performance issues in InsuranceSuite. It functions by instrumenting " stacks " of code execution and reporting the time spent in various operations like database queries or Gosu rules. According to the System Health and Quality documentation, the Profiler is categorized by how it is triggered and what it monitors.

The Web Profiler (Option A) is used to analyze performance within the user interface. When enabled, it captures the execution of a single web request (a page load or a button click), allowing the developer to see exactly which PCF widgets or page-level Gosu expressions are causing latency.

The Entry-point Profiler (Option D) is a broader category that includes profiling for non-UI operations. Entry points are the " doors " through which the application begins a task. Common entry points that can be profiled include Batch Processes, Work Queue Executors, and Web Services (API calls). By selecting an entry-point profiler, a developer can monitor the performance of background jobs or external integrations that do not have a direct UI component.

Options like Database Performance (Option B) are not specific types of the Profiler itself, but rather outcomes or areas of analysis that the profiler provides. Exit-point (Option C) and Worksheet (Option E) are not recognized classifications of the profiling tool in the Guidewire developer curriculum. Understanding these two types allows developers to strategically apply performance monitoring across the entire application stack.