Slow Response Time

Excessive Memory Consumption

Random Application termination

Failure to encrypt data

a. Filter rows when the Integration Service reads source data.

b. Join data originating from the same source database

c. Can specify a target load order based on the Source Qualifier transformations in a mapping

d. Create a custom query to issue a special SELECT statement for the Integration Service to read source data.

a. gives 1

b. throw an error

c. gives 2

d. will not evaluate.

a. Static or Dynamic Cache

b. Dynamic cache

c. static cache

d. Static and Dynamic Cache

True

False

A test environment description and test instructions.

A set of inputs, execution preconditions, and expected outcomes.

A test plan, test inputs, and logging instructions.

Execution instructions and a function description to determine correct outcome.

It enables us to reuse all our tests to improve ROI

It can be used to replace acceptance testing.

To reduce the amount of impact analysis we must do when modifying a system.

To discover any defects introduced or uncovered as a result of a change

Non-functional testing.

Structure-based testing (white box).

Static testing.

Functional testing (black box).

A goal of acceptance testing is to stress-test the system.

A goal of acceptance testing is to establish confidence in the system.

Acceptance testing is performed by technical staff.

Acceptance testing is only used to address functionality issues within the system

To help the developer to compare differences between files and databases.

To reduce the quantity of component tests needed to be run.

To make it easier for developers to peer-test each other’s code.

To simplify running unit tests when related components are not available yet.

To decide if the system is ready for detailed and further testing.

To determine how the existing system may be affected by changes.

To make use of every possible input condition as a test case.

To determine if a system can function correctly with invalid inputs.

Initiation, Preparation, Informal Review Meeting, Status, Rework, and Follow up.

Planning, Preparation, Technical Review, Rework, and Closure.

Preparation, Inspection, Rework, Closure, and Follow up.

Planning, Kick off, Individual Preparation, Review Meeting, Rework, and Follow up.

A test environment description and test instructions

A set of inputs, execution preconditions, and expected outcomes

A test plan, test inputs, and logging instructions.

Execution instructions and a function description to determine correct outcome

Agile testing methodology

Effective use of tools

Configuration management

Requirements traceability matrix

I, II and IV

I and III

III and IV

I, III and IV

Requirement specifications, test plan, code, memory leaks

Requirement specifications, test cases, user guides.

Requirement specifications, user guides, performance

Requirement specifications, website, code, use cases

Static analysis tools can change the code to reduce complexity.

Static analysis tools are intended to support developers only

Static analysis tools aid in understanding of code structure and dependencies

Static analysis tools cannot be used to enforce coding standards.

Testing ensures that the system under test will not error out in a production environment

Testing identifies defects which ensures a successful product will be released to market

Testing increases the quality of a software system by avoiding defects in the system under test.

Testing through verification and validation of functionality identifies defects in the system under test.

I

IV

I and IV

I and III

Integration of automated software test suites with the application under test.

Testing performed to expose faults in the interaction between components and systems.

Testing to verify that a component is ready for integration with the rest of the system.

Testing to verify that the test environment can be integrated with the product