Tag: testing

Questions Related to testing

  1. Member Service Representative

  2. www.usaa.com

  3. Mobile

  4. All of the above


Correct Option: D

How will u find a duplicate SSN in CBT??

  1. CBUP

  2. CBCI

  3. CBPP

  4. CBCP


Correct Option: A

when u cancel a policy, a member will be able to do 2 actions.. what are they..??

  1. Reinstate

  2. Reissue

  3. Both

  4. None


Correct Option: C

What is the code generated when a policy issue is complete?

  1. 7101

  2. 7102

  3. 7103

  4. 7106


Correct Option: A
  1. Policy taken date

  2. policy taken date + 1

  3. policy taken date + 1 week

  4. None


Correct Option: B
  1. Non payment cancellation

  2. New payement cancellation Answer

  3. Both

  4. None


Correct Option: A

How will you set risk code for a USAA member in CBT??

  1. CBCA

  2. CBCP

  3. CBCI

  4. All of the above


Correct Option: A

what is AA?

  1. Acceptabilty Assessment

  2. Assessing acceptance

  3. Accepatance assessment

  4. None


Correct Option: A

When software reliability measures are used to determine when to stop testing, the best types of test cases to use are those that

  1. Exercise system functions in proportion to the frequency they will be used in the released product

  2. Push the system beyond its designed operation limits and are likely to make the system fail

  3. Exercise unusual and obscure scenarios that may not have been considered in design

  4. Exercise the most complicated and the most error-prone portions of the system


Correct Option: A

AI Explanation

To answer this question, you need to understand the concept of software reliability measures and their relationship to testing.

Software reliability measures are used to assess the reliability or stability of a software system. These measures help determine when to stop testing and release the software.

Option A) Exercise system functions in proportion to the frequency they will be used in the released product - This option is the correct answer. When using software reliability measures, it is best to use test cases that mimic the frequency of system functions in the released product. By doing so, you can assess the reliability of the system based on its expected usage patterns.

Option B) Push the system beyond its designed operation limits and are likely to make the system fail - This option is incorrect. While it is important to test the system under stress or extreme conditions, this approach alone may not provide an accurate measure of software reliability. Testing beyond the designed operation limits may not reflect the actual usage of the system and may not provide a reliable indication of its stability.

Option C) Exercise unusual and obscure scenarios that may not have been considered in design - This option is incorrect. While it is important to test for unusual scenarios and edge cases, relying solely on these types of test cases may not provide a comprehensive measure of software reliability. It is best to focus on test cases that reflect the intended usage and frequency of system functions.

Option D) Exercise the most complicated and the most error-prone portions of the system - This option is incorrect. While it is important to thoroughly test complex and error-prone portions of the system, relying solely on these test cases may not provide an accurate measure of software reliability. It is best to consider the overall usage patterns and frequency of system functions when selecting test cases for software reliability measures.

The correct answer is A) Exercise system functions in proportion to the frequency they will be used in the released product. This option is correct because it ensures that the software reliability measures are based on the expected usage patterns and can provide a reliable indication of the system's stability.

What is the difference between a project risk and a product risk?

  1. A. Project risks are potential failure areas in the software or system; product risks are risks that surround the project’s capability to deliver its objectives.

  2. B. Project risks are the risks that surround the project’s capability to deliver its objectives; product risks are potential failure areas in the software or system.

  3. C. Project risks are typically related to supplier issues, organizational factors and technical issues; product risks are typically related to skill and staff shortages.

  4. D. Project risks are risks that delivered software will not work; product risks are typically related to supplier issues, organizational factors and technical issues.


Correct Option: B

AI Explanation

To answer this question, let's go through each option:

Option A) Project risks are potential failure areas in the software or system; product risks are risks that surround the project’s capability to deliver its objectives. This option is incorrect. Project risks are not limited to potential failure areas in the software or system, and product risks are not limited to the project's capability to deliver its objectives.

Option B) Project risks are the risks that surround the project’s capability to deliver its objectives; product risks are potential failure areas in the software or system. This option is correct. Project risks refer to the risks that may hinder the project's ability to achieve its objectives, such as delays, budget overruns, or resource constraints. Product risks, on the other hand, are related to potential failure areas in the software or system, such as software bugs or system failures.

Option C) Project risks are typically related to supplier issues, organizational factors, and technical issues; product risks are typically related to skill and staff shortages. This option is incorrect. While project risks can include supplier issues, organizational factors, and technical issues, they are not limited to these factors. Product risks are not typically related to skill and staff shortages.

Option D) Project risks are risks that delivered software will not work; product risks are typically related to supplier issues, organizational factors, and technical issues. This option is incorrect. Project risks are not solely about the delivered software not working, and product risks are not typically related to supplier issues, organizational factors, and technical issues.

The correct answer is B. Project risks are the risks that surround the project’s capability to deliver its objectives, while product risks are potential failure areas in the software or system.