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