![](/olcweb/styles/shared/spacer.gif) |
1 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Any change directed at a WebApp should include which of the following attributes? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | a change description |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | a statement of impact |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | a list of targets for change |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | none of the above |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
2 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Change management is best accomplished by |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | delaying all changes until the WebApp has been fully deployed, then making them in an agile manner |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | making changes as they are requested so that user needs are satisfied immediately |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | disregarding those change requests that come from defined classes of users, regardless of their global impact |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | none of the above |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
3 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) When change control is implemented in a WebE context, a class 1 change: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | requires a review by both technical and business managers |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | can be ignored in most instances |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | can be implemented with little formal control |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | can be implemented only after a written description is developed |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
4 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which classes of change should be handled through an agile, but formally documented review process? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | 1, 2, 3, and 4 |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | 1 and 2 |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | 3 and 4 |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | Only 4 |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
5 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) How can an organization ensure that changes have been properly implemented? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | conduct pair walkthroughs and change management audits |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | carefully document the change process |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | allow only some people to make changes |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | trust the WebE team to implement the change |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
6 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) A content management system has three distinct subsystems. These are: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | implementation, review, and auditing |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | analysis, design, and construction |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | collection, management, and publishing |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | none of the above |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
7 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following is not a criteria for determining whether a formal CMS (Content Management Systems) is required? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | content volume |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | contributor population |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | change volume |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | complexity of the WebApp functionality |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | All are valid criteria |
![](/olcweb/styles/shared/spacer.gif) |