100% satisfaction guarantee Immediately available after payment Both online and in PDF No strings attached
logo-home
Guidewire Best Practices Exam study guide questions with Complete Solutions $13.49   Add to cart

Exam (elaborations)

Guidewire Best Practices Exam study guide questions with Complete Solutions

 1 view  0 purchase
  • Course
  • GAC
  • Institution
  • GAC

Guidewire Best Practices Exam study guide questions with Complete Solutions

Preview 3 out of 24  pages

  • September 19, 2024
  • 24
  • 2024/2025
  • Exam (elaborations)
  • Questions & answers
  • GAC
  • GAC
avatar-seller
KenAli
Guidewire Best Practices Exam study
guide questions with Complete
Solutions

Logging is - Ans The process of recording application actions and state to a secondary interface


Logging is used for - Ans Application maintenance and troubleshooting
Creating statistics relating to application usage
Auditing by capturing significant events


Typical events to log are - Ans Success / Failure - a transaction or action has succeeded or failed
Recovery - a system went down or connection failed, retried, and recovered
Identification - any large functional areas such as integration, rating, reinsurance, and rules


Logging components - Logger - Ans has a category and level, sends content to an Appender


Logging components - Appender - Ans is an output destination (server console or rolling file)


Logging components - Layout - Ans defines the format of the content sent to an appender


Logging Level - Trace - Ans Description: Fine-grained informational events
When to use: Log method entry and exit

,Logging Level - Debug - Ans Description: Detailed informational events
When to use: Log important steps and calculations for diagnosing problems


Logging Level - Info - Ans Description: Coarse-grained informational messages of progress
When to use: Log the occurrence or result of an important event


Logging Level - Warn - Ans Description: Indicate a potential problem
When to use: The user experience has not been affected


Logging Level - Error - Ans Description - Indicate definite problems
When to use: The user experience has been affected


There are 2 ways to initialize a logger in Gosu - Ans Integration:
PLLoggerCategory.INTEGRATION
Plugin: PLLoggerCategory.PLUGIN


Use sub-level of existing logging category to maintain structure.


Example: PLUGIN.MotorVehicleRecord



static var _motorVehiclePluginLogger =
LoggerFactory.getLogger(PLLoggerCategory.PLUGIN."MotorVehicleRecord")


Logging Format should be - Ans a standard format to simplify analysis of large logs



Guarded Logging should be used - Ans To test log level before logging costly messages (those
with expensive expressions)

, Typically used with the DEBUG level
Format is - if (_logger.DebugEnabled) { <log statement content>}
Not required for parameterized expressions lacking expensive operations, as in:


var hello = "Hello"
var world = "world"
_logger.debug("{}, {}!", hello, world)


Logging: Exception Messages - Ans Logged at the ERROR level when user interface is affected
Not all exceptions are errors - if they are expected, log at WARN or INFO level
Pass the exception object as the second argument



Logging Guidelines - Ans Log with enough information to explain the state of the
application and what was happening
Excessive logging results in large logs with potential performance risk
Insufficient logging results in logs that lack utility


Use care with:
Data that is protected by legal, regulatory, or contractual obligations
Personally Identifiable Information (PII) - do not log PII at all!



Guidewire Query API General Best Practices - Ans Use the property reference
(EntityType#Property) for type-safe access to the properties on the query entity type

Use the property reference to filter query results, join to another entity type, order rows in
the result set, or to specify a column for a row query

Use query.contains() after other query.compare() operations against indexed columns
for better performance against large data sets

The benefits of buying summaries with Stuvia:

Guaranteed quality through customer reviews

Guaranteed quality through customer reviews

Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.

Quick and easy check-out

Quick and easy check-out

You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.

Focus on what matters

Focus on what matters

Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!

Frequently asked questions

What do I get when I buy this document?

You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.

Satisfaction guarantee: how does it work?

Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.

Who am I buying these notes from?

Stuvia is a marketplace, so you are not buying this document from us, but from seller KenAli. Stuvia facilitates payment to the seller.

Will I be stuck with a subscription?

No, you only buy these notes for $13.49. You're not tied to anything after your purchase.

Can Stuvia be trusted?

4.6 stars on Google & Trustpilot (+1000 reviews)

75759 documents were sold in the last 30 days

Founded in 2010, the go-to place to buy study notes for 14 years now

Start selling
$13.49
  • (0)
  Add to cart