Page | 1
GUIDEWIRE BEST PRACTICES EXAM 2025|
BRAND NEW ACTUAL EXAM WITH 100%
VERIFIED QUESTIONS AND CORRECT
SOLUTIONS| GUARANTEED VALUE PACK| ACE
YOUR GRADES.
Source Code Control Key Concepts
Merge in Git: - correct answer - A merge integrates changes
between branches -
Merge is a non-destructive operation that does not alter existing
commits
Adds new commit to branch history
, Page | 2
Use on shared branches (master, develop, release)
Source Code Control Key Concepts
Rebase in Git: - correct answer - A rebase integrates changes
between branches -
Creates new commits for each commit in your branch up to
common ancestor of branch you are rebasing into
Rewrites history of your branch up to common ancestor
Use only on branches that are not shared (user story, defect)
Source Code Control Key Concepts
Bitbucket Server: - correct answer - Is used as the remote code
repository for Git
Facilitates code reviews by means of pull requests
Supports various Git development workflows
Can automatically propagate merge changes from earlier to later
branches
Source Code Control Key Concepts
User story development with Git - Clone, Checkout, Stage,
Commit, Push: - correct answer - Clone remote repository to
, Page | 3
duplicate it on your local repository (Fetch to retrieve latest
changes to existing local repository)
Checkout the files in your working directory to create a local
branch off develop
Stage changes locally - use task-level commits as work is
completed
▪ Git status command displays both staged and unstaged
changes
▪ Git add command to add files to commit to staging area
Commit changes added to staging area to create a new snapshot
of the project (stores modified and added files and a point to
previous version of unmodified files)
Push user story branch back to origin (the remote repository)
Source Code Control Key Concepts
Branching Strategy - Branch: Production - correct answer -
Description: Contains code currently in production
Naming convention: master
Created: Start of new implementation
Deleted: n/a
Source Code Control Key Concepts
, Page | 4
Branching Strategy - Branch: Product Release - correct answer -
Description: Contains changes for new Guidewire product
versions
Naming convention: gw-releases
Created: Off master at beginning of project
Deleted: n/a
Source Code Control Key Concepts
Branching Strategy - Branch: Mainline - correct answer -
Description: Contains code across all releases
Naming convention: develop
Created: At beginning of project
Deleted:
Source Code Control Key Concepts
Branching Strategy - Branch: User Story - correct answer -
Description: Create off develop to deliver a user story
Naming convention: user/{user_id}/{US_id}
Created: When development begins
Deleted: When story accepted
GUIDEWIRE BEST PRACTICES EXAM 2025|
BRAND NEW ACTUAL EXAM WITH 100%
VERIFIED QUESTIONS AND CORRECT
SOLUTIONS| GUARANTEED VALUE PACK| ACE
YOUR GRADES.
Source Code Control Key Concepts
Merge in Git: - correct answer - A merge integrates changes
between branches -
Merge is a non-destructive operation that does not alter existing
commits
Adds new commit to branch history
, Page | 2
Use on shared branches (master, develop, release)
Source Code Control Key Concepts
Rebase in Git: - correct answer - A rebase integrates changes
between branches -
Creates new commits for each commit in your branch up to
common ancestor of branch you are rebasing into
Rewrites history of your branch up to common ancestor
Use only on branches that are not shared (user story, defect)
Source Code Control Key Concepts
Bitbucket Server: - correct answer - Is used as the remote code
repository for Git
Facilitates code reviews by means of pull requests
Supports various Git development workflows
Can automatically propagate merge changes from earlier to later
branches
Source Code Control Key Concepts
User story development with Git - Clone, Checkout, Stage,
Commit, Push: - correct answer - Clone remote repository to
, Page | 3
duplicate it on your local repository (Fetch to retrieve latest
changes to existing local repository)
Checkout the files in your working directory to create a local
branch off develop
Stage changes locally - use task-level commits as work is
completed
▪ Git status command displays both staged and unstaged
changes
▪ Git add command to add files to commit to staging area
Commit changes added to staging area to create a new snapshot
of the project (stores modified and added files and a point to
previous version of unmodified files)
Push user story branch back to origin (the remote repository)
Source Code Control Key Concepts
Branching Strategy - Branch: Production - correct answer -
Description: Contains code currently in production
Naming convention: master
Created: Start of new implementation
Deleted: n/a
Source Code Control Key Concepts
, Page | 4
Branching Strategy - Branch: Product Release - correct answer -
Description: Contains changes for new Guidewire product
versions
Naming convention: gw-releases
Created: Off master at beginning of project
Deleted: n/a
Source Code Control Key Concepts
Branching Strategy - Branch: Mainline - correct answer -
Description: Contains code across all releases
Naming convention: develop
Created: At beginning of project
Deleted:
Source Code Control Key Concepts
Branching Strategy - Branch: User Story - correct answer -
Description: Create off develop to deliver a user story
Naming convention: user/{user_id}/{US_id}
Created: When development begins
Deleted: When story accepted
