![](/olcweb/styles/shared/spacer.gif) |
1 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following “quality dimensions” are applicable for WebApps: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | usability, performance, interoperability |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | security, maintainability, navigability |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | content, structure, function |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
2 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Although it is possible to start WebApp "testing" in many places, it is best to begin with: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | content |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | function |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | behavior |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | security |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
3 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) When a testing plan is created, it’s intent is to: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | define testing tasks, work products, and modes of evaluation |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | create a document that describes a WebE team’s complete approach to quality assurance |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | focus exclusively on the evaluation of all use cases |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | all of the above |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
4 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The WebApp testing process exercises all elements of the design pyramid. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | true |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | false |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
5 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) An objective of content testing is: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | to uncover syntactic errors (e.g., typos, grammar mistakes) in text-based documents, graphical representations, and other media |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | to uncover semantic errors (i.e., errors in the accuracy or completeness of information) in any content object presented as navigation occurs |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | to find errors in the organization or structure of content that is presented to the end-user |
| ![](/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) |
6 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) It is always possible to perform content testing by exercising content that resides within the WebApp itself. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | true |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | false |
![](/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 question which would be asked during semantic content testing? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | Is the information up to date and factually accurate? |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | Is the information concise and to the point? |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | Is the layout of the content object easy for the user to understand? |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | Are there any typos or grammatical errors? |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | Have proper references been provided for all information derived from other sources? |
| ![](/olcweb/styles/shared/spacer.gif) | F)![](/olcweb/styles/shared/spacer.gif) | Is the information presented consistent internally and consistent with information presented in other content objects? |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
8 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Database testing for WebApps is complicated because: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | the database server sits on the same host as the Web server |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | raw data acquired from the database must first be properly formatted by the WebApp |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | the database will typically have complex schemas |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
9 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) During interface testing, the primary goal—once the WebApp has been constructed— is to ensure that generic quality criteria established for all user interfaces have been achieved. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | true |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | false |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
10 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) A viable interface testing strategy includes: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | testing Interface features to ensure that design rules, aesthetics, and related visual content are available to the user without error |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | testing interface mechanisms within the context of a use case or navigation pathway for a specific user category |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | testing within a variety of environments (e.g., operating systems, browsers) to ensure that the interface will be compatible |
| ![](/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) |
11 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Which of the following issues is not part of the overall objective of usability testing? |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | personalization |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | accessibility |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | layout |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | maintainability |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
12 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Compatibility testing focuses on |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | whether the WebApp is compatible with the needs of all user categories |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | whether the WebApp is compatible with the many variants encountered within the client side environment |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | whether the WebApp is compatible with the business objectives of the organization that has sponsored it |
| ![](/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) |
13 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Equivalence partitioning, boundary value analysis and path testing are often applied as part of |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | algorithm testing |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | navigation testing |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | component testing |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | database testing |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
14 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) A navigation semantic unit is |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | a testing approach for user interfaces |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | a metric that can be applied to assess the completeness of navigation testing |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | a testing "unit" that can provide guidance for test planning |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | a set of information and related navigation structures that collaborate in the fulfillment of a related user requirements |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
15 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Configuration testing should focus only on the client side. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | true |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | false |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
16 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Security testing is best left to professional who specialize in the subject, particularly for complex, business critical WebApps. |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | true |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | false |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
17 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) The following expression, P = N x T x D, is used to compute: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | payload |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | throughput |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | performance |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | security |
![](/olcweb/styles/shared/spacer.gif) |
![](/olcweb/styles/shared/spacer.gif) |
18 | ![](/olcweb/styles/shared/spacer.gif) | ![](/olcweb/styles/shared/spacer.gif) Stress testing does not address which of the following questions: |
| ![](/olcweb/styles/shared/spacer.gif) | A)![](/olcweb/styles/shared/spacer.gif) | Does the system degrade "gently" or does the server shut down as capacity is exceeded? |
| ![](/olcweb/styles/shared/spacer.gif) | B)![](/olcweb/styles/shared/spacer.gif) | Does server software generate "server not available" messages? More generally, are users aware that they cannot reach the server? |
| ![](/olcweb/styles/shared/spacer.gif) | C)![](/olcweb/styles/shared/spacer.gif) | Will the server overheat as the load increases? |
| ![](/olcweb/styles/shared/spacer.gif) | D)![](/olcweb/styles/shared/spacer.gif) | Are transactions lost as capacity is exceeded? |
| ![](/olcweb/styles/shared/spacer.gif) | E)![](/olcweb/styles/shared/spacer.gif) | If the system does fail, how long will it take to come back online? |
![](/olcweb/styles/shared/spacer.gif) |