Confuse Skull: Continuous Deployment MCQ's

Continuous Deployment MCQ's

1. Capacity testing _.

is a critical testing and helps to verify technical aspects

2. Accurev is a _ system.

Stream Based Version Control

3. ____________ testing was derived from hardware testing.

Smoke

4. The continuous deployment must be followed to practice continuous delivery.

True

5. Large scale changes to an application can be achieved using __.

Branch by Abstraction

6. Collection of executable codes is known as .

Binaries

7. A build can be triggered by a version control tool.

True

8. A build that fails __ stage will not be deployable.

Acceptance

9. People who do the deployment should be part of creating the deployment process.

True

10. Dependencies between components must be represented using .

Directed acyclic graph

11. Time taken to fix a broken build is measured using __.

Build repair rate

12. Build-time dependency should be present when an application is run.

False

13. Build tools can be categorised as ____.

Both the options

14. Release candidate is created after the change passes through the .

Commit Stage

15. New instance of ___ is created upon every check-in.

All of the options

16. Continuous deployment aims at making feedback loops as short as possible.

True

17. _ is a paradigm to move code from check-in to production in a controlled way.

Integration Pipeline

18. Feature toggles is possible in version control systems.

True

19. User acceptance testing is a verification activity.

False

20. Disciplined technique for restructuring a code without modifying its external behavior is _.

Refactoring

21. Famous problem of dependency management is known as ___.

DLL Hell

22. Only positive scenarios are validated in ___ testing.

Build Verification

23. MTTR is ____.

Mean Time to Repair failures.

24. Automated implementation of an application's build, test, and deployment process is called as _.

Deployment Pipeline

25. The deployment pipeline is initiated by the creation of a release candidate.

False

26. _ stage asserts that the system works at the technical level.

Manual Test

27. The capability of your build system to handle an increase in the amount of code that it integrates and analyzes is known as .

Build performance

28. Chef is an orchestration tool.

True

29. In branch by abstraction model, features are developed in _.

Release Branch

30. Steps to be followed to release the application first time is part of ___.

Release Plan

31. Static code analysis is performed in the _.

Commit stage

32. User acceptance testing is done in the stage.

Manual Test

33. Functional testing is a verification activity.

True

34. Testing done in a customer's environment is know as .

Beta

35. Value delivered by an application is validated through .

All of the options

36. _ is a central part of continuous deployment.

Deployment Pipeline

37. ____ stage takes the delivery team beyond continuous integration.

Acceptance

No comments:

Post a Comment