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