February 2019

A. Business impact risks
B. Process definition risks
C. Product size risks
D. Development environment risks

A. Risk identification
B. Performance risk
C. Support risk
D. Risk projection

Explanation: By identifying known and predictable risks, the project manager takes a first step toward avoiding them when possible and controlling them when necessary.

A. Known risks
B. Business risks
C. Project risks
D. Technical risks

Explanation: Technical risks identify potential design, implementation, interface, verification, and maintenance problems.

A. building an excellent product or system that no one really wants
B. losing the support of senior management due to a change in focus or change in people
C. lack of documented requirements or software scope
D. losing budgetary or personnel commitment

Explanation: This is not considered as a business risk.

A. Business impact risks
B. Process definition risks
C. Product size risks
D. Development environment risks

A. Known risks
B. Business risks
C. Project risks
D. Technical risks

Explanation: Business risks often jeopardize the project or the product

A. Risk exposure
B. Risk prioritization
C. Risk analysis
D. All of the mentioned

A. Constructive cost model
B. Comprehensive cost model
C. Constructive cost estimation model
D. Complete cost estimation model

A. Risk assessment
B. Risk generation
C. Risk control
D. None of the mentioned

Explanation: Risk management activities would never want a new risk to be generated.

A. FP-Based Estimation
B. Process-Based Estimation
C. COCOMO
D. Both FP-Based Estimation and COCOMO

Explanation: Function points and COCOMO are used to evaluate effort.