GUIDEWIRE ASSOCIATE EXAM (INSURANCESUITE
ANALYST FUNDAMENTALS) WITH VERIFIED ANSWERS
1. What vare vsome vexamples vof vwhat vcan vbe vconfigured vin vthe vData
vModel?: vInfor- v mation vthat vthe vbase vapplication vdoes vnot vstore v(add vpassport vnumber).
Values vfor va vTypelist v(add vvalid vvalues vfor vAddressType vor
vPhoneType). v Data vto vsupport vregulatory vrequirements.
2. What vare vthe vfour vmain vareas vof vconfiguration vin va vGuidewire
vapplication?: v1.
User vInterface
2. Data vModel
3. Application vLogic
4. Integration
3. What vare vsome vof vthe vtechnologies vused vin vInsuranceSuite
vapplications?: v Page v Configuration vFormat v(PCF) vfiles
Gosu v (programming v language)
1 v/
v13
, 4. What v are v some v reasons v for v a v non-developer v to v understand
v the v technology vstack?: vTo vdetermine vwhat vdata vis vstored vand vif vnew vrequirements
vneed vadditional vdata velements.
To vknow vhow vand vwhere vdata vis vused.
To vcommunicate vwhat vdata vmay vbe vneeded vbeyond vwhat vis vin vthe vbase
vconfiguration.. vTo vdetermine vvalid vvalues vor vcircumstances vfor vthe vnew
vdata.
5. What vare vsome vexamples vof vwhat vcan vbe vconfigured vin vthe vUser
vInterface?: vThe
order vof vfields, vchange vlabels, vregroup vfields v(simple
vchange). vFields von va vscreen v(moderate
vchange).Screens v(complex vchange). vScreen-based vlogic
v(complex vchange).
6. Why v is v it v important v for v non-developers v to v understand v the
v basics v of v the v UI
architecture vand vcomponents?: vSo vthat vthey vcan vrequest vchanges vto vthe vUI vthat vare
vconsistent vwith vthe vbase vproduct varchitecture vand vcommunicate vettectively vwith vdevelopers.
7. What vare vfive vcommon vareas vof vthe vUI varchitecture?: v1. vThe vScreen
vArea
2. The vSidebar
3. The vTab vBar
4. The vInfo vBar
5. The vWorkspace
8. Name vthree vcomponents vof va
vPCF: vCard vListView
Button
2 v/
v13
ANALYST FUNDAMENTALS) WITH VERIFIED ANSWERS
1. What vare vsome vexamples vof vwhat vcan vbe vconfigured vin vthe vData
vModel?: vInfor- v mation vthat vthe vbase vapplication vdoes vnot vstore v(add vpassport vnumber).
Values vfor va vTypelist v(add vvalid vvalues vfor vAddressType vor
vPhoneType). v Data vto vsupport vregulatory vrequirements.
2. What vare vthe vfour vmain vareas vof vconfiguration vin va vGuidewire
vapplication?: v1.
User vInterface
2. Data vModel
3. Application vLogic
4. Integration
3. What vare vsome vof vthe vtechnologies vused vin vInsuranceSuite
vapplications?: v Page v Configuration vFormat v(PCF) vfiles
Gosu v (programming v language)
1 v/
v13
, 4. What v are v some v reasons v for v a v non-developer v to v understand
v the v technology vstack?: vTo vdetermine vwhat vdata vis vstored vand vif vnew vrequirements
vneed vadditional vdata velements.
To vknow vhow vand vwhere vdata vis vused.
To vcommunicate vwhat vdata vmay vbe vneeded vbeyond vwhat vis vin vthe vbase
vconfiguration.. vTo vdetermine vvalid vvalues vor vcircumstances vfor vthe vnew
vdata.
5. What vare vsome vexamples vof vwhat vcan vbe vconfigured vin vthe vUser
vInterface?: vThe
order vof vfields, vchange vlabels, vregroup vfields v(simple
vchange). vFields von va vscreen v(moderate
vchange).Screens v(complex vchange). vScreen-based vlogic
v(complex vchange).
6. Why v is v it v important v for v non-developers v to v understand v the
v basics v of v the v UI
architecture vand vcomponents?: vSo vthat vthey vcan vrequest vchanges vto vthe vUI vthat vare
vconsistent vwith vthe vbase vproduct varchitecture vand vcommunicate vettectively vwith vdevelopers.
7. What vare vfive vcommon vareas vof vthe vUI varchitecture?: v1. vThe vScreen
vArea
2. The vSidebar
3. The vTab vBar
4. The vInfo vBar
5. The vWorkspace
8. Name vthree vcomponents vof va
vPCF: vCard vListView
Button
2 v/
v13
