Developing in the Cloud - InsuranceSuite Developer Fundamentals

Cloud Assurance

Ensures the readiness of an implementation for Cloud deployment

False

(True/False) Cloud Assurance replaces the need for a dedicated implementation team

True

(True/False) Trained and certified team members are essential for a successful Cloud Implementation

Leads

Team members who complete the most advanced training and achieve Certified Ace competency

Associates

Team members who complete the essential trainings and achieve Certified Associate competency

3

How many associates a single lead can support, according to the required ratio

Cloud Delivery Standards

Proven principles and practices that include implementation requirements, specifications, and guidelines

Cloud Assurance Assessments

CAA abbreviation stands for

True

(True/False) The goal of Cloud Assurance Assessments (CAAs) is to verify the solution and code are optimized for Guidewire Cloud.

True

(True/False) Cloud Assurance Assessments (CAAs) are continual and build on prior assessments

True

(True/False) Cloud Assurance Assessments are required for brand new Guidewire cloud implementations.

True

(True/False) Cloud Assurance Assessments are required for all Guidewire cloud upgrades.

False

(True/False) Cloud Assurance Assessments are required for self-managed non-cloud implementations.

True

(True/False) Cloud Assurance Assessments are required for post-production releases of Guidewire Cloud products.

Security

This type of cloud assessment ensures security vulnerabilities have not been introduced and verifies that there is no capturing of secret data

Operations

This type of cloud assessment ensures applications have monitoring and logging frameworks in place and that knowledge transfer documentation is complete

Performance

This type of cloud assessment checks for designs and product usage that may violate or introduce performance risks to the Guidewire applications

Upgrades

This type of cloud assessment reviews feature and integration designs for product alignment, upgradeability, code quality, and so on

Optimization Backlog

A sheet which identifies optimizations required to ensure predictable entry to Guidewire Cloud

Pre-Inception

The 1st phase of a Guidewire Cloud upgrade project

Inception

The 2nd phase of a Guidewire Cloud upgrade project, following Pre-Inception and coming before Development

Development

The 3rd phase of a Guidewire Cloud upgrade project, following Inception and coming before Stabilization

Stabilization

The 4th phase of a Guidewire Cloud upgrade project, following Development and coming before Deployment Prep

Deployment Prep

The 5th phase of a Guidewire Cloud upgrade project, following Stabilization and coming before Deployment

Deployment

The 6th and final phase of a Guidewire Cloud upgrade project

Remediation

The process of reviewing existing data and fixing it to ensure it complies with Guidewire standards, done to all optimization items after every assessment

User Acceptance Testing

UAT abbreviation stands for

True

(True/False) The Operations assessment ensures applications have monitoring and logging frameworks in place

True

(True/False) All optimization items must be remediated before deployment to Cloud

Distributed Version Control System

DVCS abbreviation stands for

Git

A distributed version control system using branches that treats data as a series of snapshots of all the files in a project

Commit

In Git, a snapshot of all the files in a project

True

(True/False) Git Commits are chained together.

False

(True/False) Git files are versioned individually.

True

(True/False) In Git, the entire project is versioned instead of the individual files.

Branch

In Git, a floating pointer to a given stream of commits

False

(True/False) Git Branches are expensive to create.

True

(True/False) Merging changes between branches in Git is (slightly) costly.

Tag

In Git, a fixed pointer to a specific commit with an easily readable name

False

(True/False) A Git Merge is an inherently destructive operation, as it alters the existing commits

True

(True/False) A Git Merge adds a new commit to your branch history.

True

(True/False) A Git Rebase fundamentally rewrites history data.

False

(True/False) You should use Git Rebase on shared branches.

True

(True/False) You should use Git Merge on shared branches.

Bitbucket

A web-based code hosting system that supports Git repositories, and the preferred Git hosting software by Guidewire

Pull Request

A formal request to merge code from one branch to another which requires a review and specific user-defined criteria

git clone

The console command to clone a Git repository

git fetch

The console command to make your local Git repository aware of changes made to the remote

git checkout

The console command to switch from one Git branch to another

git status

The console command to check the current state of your Git repository, including which files were changed and which have yet to be staged still

git add

The console command to stage local Git changes

git commit

The console command to create a new Git commit

-m

The console argument used with git commit to define the message for the commit

git rebase

The console command to rebase one Git branch onto another

git push

The console command to push local Git commits up to the remote

git pull

The console command to pull new commits from the remote branch down to the local Git branch

git log

The console command to view the history of the current Git branch

git revert

The console command to revert or undo a specific commit, given its checksum

master

The name of the main branch in a Guidewire project which updates when the production system is updated

develop

The name of the mainline code branch in a Guidewire project which updates as development work progresses

gw-releases

The name of the product release branch in a Guidewire project which hosts new Guidewire product versions

release/

The name of the branch header used to tag new project release branches which contain stable customer releases

Hotfix

The type of branch used to fix production issues quickly when they require a quick fix

User Story

The type of branch used for the development of new functionality tied to a user story during a sprint

Defect

The type of branch used to fix significant issues detected at any stage of the implementation, not just in production

False

(True/False) The master branch should be writable by all implementation team members

True

(True/False) Any developer on the team can merge code to the develop branch

hotfix/

The name of the branch header used to tag hotfix branches

user/

The name of the branch header used to tag user story branches

user/shared/

The name of the branch header used to tag shared user branches, when more than one developer needs to work on a user story

Archiving

The process of serializing, persisting, and removing archivable objects from the main data store to preserve application performance

config.xml

The parameters that control archiving are stored in this configuration file

Extractable

In order to be archived, an entity must implement this delegate

True

(True/False) An entity must have a foreign key relationship to an entity in the archive domain graph in order to be archived

Archive Item Writer

The batch process that checks for parent entities that fit the archival criteria and archives them along with their associated objects

Archive Search Interface

The archiving component that finds summary information about the archived items

Archive Retrieval Process

The process that retrieves the archive from the data store

True

(True/False) The archive retrieval process returns the retrieved item to a state of existence as if archiving never happened.

False

(True/False) The archiving item writer batch process is scheduled to run automatically in the base configuration.

True

(True/False) The archiving item writer batch process can be run manually from the Server Tools screen.

False

(True/False) The process of searching for archived Claims, PolicyPeriods, or PolicyTerms is different from searching for non-archived versions of these objects

implementsEntity

In an ETI file, this field can be added to the entity to implement a delegate.

True

(True/False) In the archiving graph, a new entity must also be owned by an existing entity in the graph.

archivingOwner

The foreign key property that must be used to link an owner entity to a new entity in the archiving graph.

Reference Data

The common term for non-graph entities, in reference to archiving

True

(True/False) Admin data, system data, and cross-parent data are all examples of non-graph entities

False

(True/False) Admin data, system data, and cross-parent data are all examples of graph entities

True

(True/False) Non-graph entities must be retireable.

True

(True/False) Non-graph entities must have no foreign key relationship from the new entity to the graph and can have instances referenced by multiple graph instances

Overlap Entity

An entity with some rows that are inside the archive graph and other rows that are outside the archive graph

False

(True/False) Overlap entities are extremely common occurrences.

OverlapTable

Overlap entities must implement this unique delegate alongside the common Extractable delegate.

DOT

A plain text graph description language used to produce a graphical description of the data model

False

(True/False) Archiving has no impact on system performance.

True

(True/False) Archiving helps with system performance.

True

(True/False) Archiving is about removing information from the main data store that is no longer used and will never be used again.