What is the difference between the process configuration that comes from a shared project area process and one that comes from a process template?

What is the difference between the process configuration that comes from a shared project area process and one that comes from a process template. Is there something that I can configure in one that I cannot with the other?
For example:
I need to standardize all project areas in one repository. I can do this by creating a Master Project Area, configure its process and share the process with all other project areas or I can create a process template and use it to create all the project areas in the repository. What's the difference between doing one way or the other?
Accepted answer

If using a process template, once you create a project out of it, there is no longer any links between the project and the template.
If using a master project, as long as you don't override the configuration in the child projects, any configuration changes in the master project will be inherited by the child projects automatically.