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