A) Only the source code of the software B) Helps new team members onboard quickly C) Written text and illustrations describing architecture, design, functionality, and usage
A) Only the description of what the endpoint does B) Only the HTTP methods C) Purpose, expected behavior, URL route, and HTTP methods
A) OPEN, CLOSE, SAVE, LOAD B) START, STOP, PAUSE, RESUME C) GET, POST, PUT, DELETE
A) Using inline comments to explain complex logic B) Adding redundant comments that restate obvious code C) Avoiding any comments in the code
A) To debug the code B) Standardized descriptions for functions, classes, or modules C) . To store data in the program
A) HTML format B) PEP 257 C) Javadoc style
A) Javadoc B) Doxygen C) Confluence
A) To generate structured documentation from reStructuredText and docstrings B) To design user interfaces C) To compile code into executable files
A) Apache License 2.0 B) MIT License C) Creative Commons
A) Apache License 2.0 B) MIT License C) Creative Commons
A) Software only B) Media and documents, not software C) Hardware designs
A) It protects intellectual property and clarifies usage rights B) It makes the software harder to use C) It is not necessary for open-source projects
A) The ability to perform required functions under stated conditions without failure B) The ability to handle unexpected inputs without crashing C) The ability to be easily modified
A) Redundancy B) Recovery Mechanisms C) Error Detection & Correction
A) Redundancy B) Automated testing C) Check sums, parity bits, and validation rules
A) Automated testing B) Performance testing C) User acceptance testing
A) Using parity bits B) Checkpointing and rollback in databases C) Duplicating servers
A) To increase the number of tools used B) To avoid following any conventions C) To ensure code and systems are clear, maintainable, and legally safe
A) Postman B) Swagger / OpenAPI C) RAML
A) API testing and documentation B) Creating documentation websites C) Designing API schemas
A) Redoc and MkDocs B) RAML and API Blueprint C) Swagger and OpenAPI
A) Sphinx B) Redoc C) Postman
A) message B) parameters C) status
A) daily.temp.min B) daily.feels_like C) daily.temp.max
A) Ability to handle unexpected inputs without crashing B) Ability to duplicate critical components C) Optimal use of resources (time, memory, CPU) while delivering results quickly
A) Checkpointing and rollback in databases, retry logic B) Duplicating critical components C) Using parity bits to detect errors
A) Adding more servers B) Using binary search instead of linear search for large datasets C) Using linear search instead of binary search B. Using binary search instead of linear search for larg
A) Ability to perform functions without failure over time B) Ability to duplicate critical components for fault tolerance C) Optimal use of resources (time, memory, CPU, network) while delivering results quickly
A) Database Optimization B) Algorithmic Optimization C) Caching & Memoization
A) To identify performance bottlenecks using tools B) To use multithreading C) To avoid memory leaks
A) Caching & Memoization B) Resource Management C) Caching & Memoization
A) Testing edge cases B) Avoiding memory leaks and releasing unused objects C) Handling exceptions
A) Algorithmic Optimization B) Parallelism & Concurrency C) Database Optimization
A) Exception handling B) Indexing, query optimization, and normalization/denormalization trade-offs C) Caching all data
A) Testing individual units of code (functions, classes, methods) in isolation B) Testing only the user interface C) Testing after full integration
A) Makes code harder to modify B) Increases development time significantly C) Improves code maintainability and reduces regression issues
A) Testing only once before release B) Frequently integrating code into a shared repository and running automated tests C) Working on code in isolation without sharing
A) To delay integration until the end B) To reduce the number of tests C) To ensure new code does not break existing functionality
A) Ability to recover from failures automatically B) Ability to handle unexpected situations gracefully without crashing or incorrect results C) Ability to use resources optimallyWhich practice involves never trusting user input and checking ranges, types, and formats?
A) Fail-Safe Defaults B) Input Validation C) Exception Handling
A) Testing only valid inputs B) Using try/except blocks C) Testing minimum, maximum, and out-of-range values
A) if/else B) try/except C) loops
A) Allowing any input without checks B) Showing technical errors to users C) Defaulting to secure/safe behavior if inputs are invalid
A) Avoiding any error handling B) Anticipating and guarding against potential failures C) Writing complex code to prevent errors
A) To retry failed operations B) To define preconditions, postconditions, and invariants C) To log runtime information
A) Ignoring failed operations B) Automatically retrying operations like API calls if they fail C) Stopping the system on failure
A) To collect runtime information for debugging and failure analysis B) To speed up the code C) To prevent errors from happening
A) Implementing watchdogs or self-healing services B) Ignoring failures C) Manually fixing errors
A) JUnit B) Jest C) pytest
A) Code that does not have any error handling B) A login form that handles incorrect passwords gracefully without crashing C) Code that only works with perfect inputs |