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) Purpose, expected behavior, URL route, and HTTP methods B) Only the description of what the endpoint does C) Only the HTTP methods
A) GET, POST, PUT, DELETE B) START, STOP, PAUSE, RESUME C) OPEN, CLOSE, SAVE, LOAD
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 store data in the program B) To debug the code C) Standardized descriptions for functions, classes, or modules
A) PEP 257 B) Javadoc style C) HTML format
A) Confluence B) Javadoc C) Doxygen
A) To design user interfaces B) To generate structured documentation from reStructuredText and docstrings C) To compile code into executable files
A) MIT License B) Apache License 2.0 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 is not necessary for open-source projects B) It makes the software harder to use C) It protects intellectual property and clarifies usage rights
A) The ability to handle unexpected inputs without crashing B) The ability to be easily modified C) The ability to perform required functions under stated conditions without failure
A) Error Detection & Correction B) Recovery Mechanisms C) Redundancy
A) Redundancy B) Automated testing C) Check sums, parity bits, and validation rules
A) User acceptance testing B) Automated testing C) Performance testing
A) Using parity bits B) Checkpointing and rollback in databases C) Duplicating servers
A) To avoid following any conventions B) To increase the number of tools used C) To ensure code and systems are clear, maintainable, and legally safe
A) Postman B) RAML C) Swagger / OpenAPI
A) Designing API schemas B) API testing and documentation C) Creating documentation websites
A) RAML and API Blueprint B) Swagger and OpenAPI C) Redoc and MkDocs
A) Redoc B) Postman C) Sphinx
A) message B) parameters C) status
A) daily.temp.min B) daily.feels_like C) daily.temp.max
A) Optimal use of resources (time, memory, CPU) while delivering results quickly B) Ability to handle unexpected inputs without crashing C) Ability to duplicate critical components
A) Duplicating critical components B) Using parity bits to detect errors C) Checkpointing and rollback in databases, retry logic
A) Using binary search instead of linear search for large datasets B) Adding more servers 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) Algorithmic Optimization B) Caching & Memoization C) Database Optimization
A) To avoid memory leaks B) To identify performance bottlenecks using tools C) To use multithreading
A) Caching & Memoization B) Caching & Memoization C) Resource Management
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) 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) Improves code maintainability and reduces regression issues B) Makes code harder to modify C) Increases development time significantly
A) Frequently integrating code into a shared repository and running automated tests B) Working on code in isolation without sharing 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 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 minimum, maximum, and out-of-range values B) Using try/except blocks C) Testing only valid inputs
A) loops B) if/else C) try/except
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) Writing complex code to prevent errors C) Anticipating and guarding against potential failures
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) Ignoring failed operations C) Stopping the system on failure
A) To prevent errors from happening B) To speed up the code C) To collect runtime information for debugging and failure analysis
A) Implementing watchdogs or self-healing services B) Ignoring failures C) Manually fixing errors
A) pytest B) Jest C) JUnit
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 |