Guidewire Best Practices Exam study guide Questions with Complete Solutions

Guidewire Best Practices Exam study guide Questions with Complete Solutions Package naming conventions - Answer-Use the format re Customer - company name abbreviation Application- InsuranceSuite application code (pc, bc, cc, suite) Feature Category - major feature (delinquency, configuration, integration) Feature - feature (rating, catastrophe, authentication) Example: ntication Class naming conventions - Answer-Use UpperCamelCase Do not add _Ext to classes within customer package spaces Function naming conventions - Answer-Use lowerCamelCase Use a verb that describes that the function is doing i.e. verifyAddress Do not add _Ext suffix to private functions or enhancements in customer package spaces Variable naming conventions - Answer-Member variable names use lowerCamelCase with a leading underscore i.e. _pluginCallbackHandler Local variable names use lowerCamelCase short names that describe the purpose i.e. latestPolicyRevision Display key naming conventions - Answer-Add suffix _Ext too all new display keys Do not modify automatically generated display keys Logging is - Answer-The process of recording application actions and state to a secondary interface Logging is used for - Answer-Application maintenance and troubleshooting Creating statistics relating to application usage Auditing by capturing significant events Typical events to log are - Answer-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 - Answer-has a category and level, sends content to an Appender Logging components - Appender - Answer-is an output destination (server console or rolling file) Logging components - Layout - Answer-defines the format of the content sent to an appender