A) Helps new team members onboard quickly B) Only the source code of the software C) Written text and illustrations describing architecture, design, functionality, and usage
A) Only the HTTP methods B) Purpose, expected behavior, URL route, and HTTP methods C) Only the description of what the endpoint does
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) Standardized descriptions for functions, classes, or modules B) . To store data in the program C) To debug the code
A) HTML format B) Javadoc style C) PEP 257
A) Confluence B) Doxygen C) Javadoc
A) To design user interfaces B) To compile code into executable files C) To generate structured documentation from reStructuredText and docstrings
A) Apache License 2.0 B) MIT License C) Creative Commons
A) MIT License B) Apache License 2.0 C) Creative Commons
A) Media and documents, not software B) Software only C) Hardware designs
A) It makes the software harder to use B) It is not necessary for open-source projects C) It protects intellectual property and clarifies usage rights
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) Recovery Mechanisms B) Error Detection & Correction C) Redundancy
A) Automated testing B) Check sums, parity bits, and validation rules C) Redundancy
A) Performance testing B) User acceptance testing C) Automated testing
A) Checkpointing and rollback in databases B) Duplicating servers C) Using parity bits
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) RAML B) Postman C) Swagger / OpenAPI
A) API testing and documentation B) Designing API schemas C) Creating documentation websites
A) RAML and API Blueprint B) Swagger and OpenAPI C) Redoc and MkDocs
A) Redoc B) Sphinx C) Postman
A) parameters B) status C) message
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) 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 duplicate critical components for fault tolerance B) Ability to perform functions without failure over time C) Optimal use of resources (time, memory, CPU, network) while delivering results quickly
A) Caching & Memoization B) Algorithmic Optimization C) Database Optimization
A) To avoid memory leaks B) To use multithreading C) To identify performance bottlenecks using tools
A) Caching & Memoization B) Caching & Memoization C) Resource Management
A) Handling exceptions B) Avoiding memory leaks and releasing unused objects C) Testing edge cases
A) Parallelism & Concurrency B) Database Optimization C) Algorithmic 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 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) Testing only once before release C) Frequently integrating code into a shared repository and running automated tests
A) To reduce the number of tests B) To delay integration until the end C) To ensure new code does not break existing functionality
A) Ability to handle unexpected situations gracefully without crashing or incorrect results B) Ability to recover from failures automatically C) Ability to use resources optimallyWhich practice involves never trusting user input and checking ranges, types, and formats?
A) Exception Handling B) Fail-Safe Defaults C) Input Validation
A) Using try/except blocks B) Testing minimum, maximum, and out-of-range values C) Testing only valid inputs
A) if/else B) try/except C) loops
A) Allowing any input without checks B) Defaulting to secure/safe behavior if inputs are invalid C) Showing technical errors to users
A) Writing complex code to prevent errors B) Avoiding any error handling C) Anticipating and guarding against potential failures
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 prevent errors from happening C) To speed up the code
A) Ignoring failures B) Implementing watchdogs or self-healing services C) Manually fixing errors
A) JUnit B) Jest C) pytest
A) Code that only works with perfect inputs B) Code that does not have any error handling C) A login form that handles incorrect passwords gracefully without crashing |