We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5
Mid-1
Multiple choice questions.
1. The software development lifecycle (SDLC) is a framework for: a) Project management only b) Technical development only c) The entire process of software creation d) User interface design 2. Agile development focuses on: a) Extensive planning and documentation b) Iterative development and customer feedback c) Waterfall methodology with strict deadlines d) Individual developer work with minimal collaboration 3. A short, time-boxed development cycle in Agile is called a: a) Milestone b) Release c) Sprint d) Iteration 4. DevOps aims to bridge the gap between: a) Design and development teams b) Marketing and sales teams c) Testing and deployment teams d) Development and operations teams 5. Which of the following is NOT a core DevOps practice? a) Continuous integration and continuous delivery b) Manual testing and deployment processes c) Infrastructure as code (IaC) d) Automation of repetitive tasks 6. ITIL is a framework for: a) Software development b) IT service management c) Project management d) Network security 7. Which of the following is NOT one of the cores ITIL processes? a) Incident management b) Problem management c) Change management d) User experience design 8. What is the primary focus of a DevOps engineer? a) Bridging the gap between development and operations teams. b) Writing complex backend code c) Designing user interfaces d) Managing user accounts and permissions. 9. Which of the following is a core principle of the DevOps lifecycle that promotes business agility? a) Extensive documentation and sign-offs before each step b) Rapid feedback loops and continuous delivery of value c) Siloed development and operations teams with limited communication d) Prioritization of long-term planning over quick adaptation 10. What is the main goal of continuous testing? a) To conduct exhaustive testing before each release. b) To identify and fix bugs after software is deployed to production. c) To perform manual testing only after a new feature is complete. d) To integrate automated testing throughout the development lifecycle. 11. What is a major drawback of a monolithic architecture? a) It offers high performance for all use cases. b) It’s inherently scalable and can easily handle increased load. c) Changes to one part of the application can impact the entire system, slowing down deployments. d) It provides clear separation of concerns between different application functions. 12. How can DevOps principles be applied to handle database migrations safely and efficiently? a) Manually script all migration changes and deploy them directly to production. b) Use version control for migration scripts and automate deployments with rollback capabilities. c) Perform all database changes after the application is deployed to production. d) Leave database schema changes to the database administrator without developer involvement. 13. Which of the following tools is NOT typically used for automating database migrations in DevOps? a) Version control system (e.g., Git) b) Database migration tools (e.g., FlywayDB, Liquibase) c) Continuous integration/Continuous delivery (CI/CD) pipeline d) Spreadsheets for tracking migration scripts 14. Which pioneering system is considered a major contributor to the development of modern Source Code Control tools? a) RCS (Revision Control System) b) Microsoft Visual Studio c) Git (Developed later) d) Java Development Kit (JDK) 15. What limitations did early manual version control systems have? a) They were too expensive for small companies. b) They were prone to human error and lacked efficient version tracking. c) They required specialized hardware and software. d) They were only suitable for large and complex projects. 16. What is a benefit of using Source Code Control for bug tracking and resolution? a) It obscures the history of code changes related to bugs. b) It assigns blame for bugs to specific developers. c) It allows developers to pinpoint the exact version where a bug was introduced. d) It requires manual documentation of all bug fixes. 17. How did centralized Source Code Control systems like CVS (Concurrent Versions System) improve upon manual methods? a) They offered a user interface but lacked branching capabilities. b) They provided a central repository for code, improved version tracking, and enabled collaboration. c) They were only accessible by developers with specific permissions. d) They primarily focused on security features for source code. 18. How did the introduction of distributed version control systems like Git impact the software development landscape? a) It made code management overly complex for small projects. b) It primarily focused on security features for source code. c) It required a significant change in developer workflow and tools. d) It enabled greater flexibility, offline access, and branching capabilities. 19. What was a common practice for managing code versions before centralized Source Code Control systems? a) Developers relied solely on memory to recall changes. b) Manual file copying and version numbering systems were used. c) Early developers used punch cards for each code iteration. d) There was no formal version control system in place. 20. Why is source code control essential in software development? a) It allows teams to track changes, collaborate effectively, and revert to previous versions if needed. b) It only helps manage documentation related to the code. c) It automates the entire software development process. d) It primarily focuses on security and access control for the code. Fill in the blanks. 1. The DevOps process involves a continuous delivery pipeline, where code changes are automatically _______ (integrated) into a central repository. 2. If the tests pass, the code can be _______ (deployed) to a staging environment for further testing. 3. Continuous delivery enables frequent releases of software, allowing for faster _______ (feedback) from users. 4. By automating the delivery process, _______ (errors) are minimized. 5. Continuous delivery allows for a more _______ (agile) development approach. 6. Feedback can be used to identify _______ (bugs) and improve the software. 7. An ________(Agile) framework that uses short sprints and a backlog of user stories to deliver software iteratively. 8. __________(Bottlenecks) are stages in the delivery process that slow down the overall flow. 9. The DevOps lifecycle is a continuous loop that emphasizes _______ (collaboration) between development and operations teams. 10. DevOps promotes a culture of _______ (continuous improvement), where teams constantly learn and adapt their processes. 11. These tests are run _______ (frequently), often after every code change. 12. Continuous testing provides _______ (confidence) in the quality of the software before deployment. 13. The separation of concerns principle helps to _______ (decompose) a complex system into smaller, manageable modules. 14. _______ (Loose coupling) between modules encourages reusability and reduces the impact of changes within one module on others. 15. _______ (Loose coupling) between modules encourages reusability and reduces the impact of changes within one module on others. 16. _______ (Rollback plans) should be created in case a migration encounters unexpected issues. 17. _______ (Rollback plans) should be created in case a migration encounters unexpected issues. 18. Automated testing helps to _______ (verify) the success of a migration and prevent data loss. 19. Microservices architecture promotes _______ (decentralized) data management where each service can have its own data store. 20. _______ (API gateways) can be used to manage communication between microservices and their respective data stores.