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 description of what the endpoint does B) Only the HTTP methods C) Purpose, expected behavior, URL route, and HTTP methods
A) START, STOP, PAUSE, RESUME B) GET, POST, PUT, DELETE 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) Standardized descriptions for functions, classes, or modules B) To debug the code C) . To store data in the program
A) HTML format B) Javadoc style C) PEP 257
A) Javadoc B) Confluence C) Doxygen
A) To generate structured documentation from reStructuredText and docstrings B) To design user interfaces C) To compile code into executable files
A) Creative Commons B) MIT License C) Apache License 2.0
A) Apache License 2.0 B) Creative Commons C) MIT License
A) Hardware designs B) Software only C) Media and documents, not software
A) It protects intellectual property and clarifies usage rights B) It makes the software harder to use C) It is not necessary for open-source projects
A) The ability to be easily modified B) The ability to perform required functions under stated conditions without failure C) The ability to handle unexpected inputs without crashing
A) Error Detection & Correction B) Recovery Mechanisms C) Redundancy
A) Check sums, parity bits, and validation rules B) Redundancy C) Automated testing
A) Performance testing B) Automated testing C) User acceptance 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) RAML B) Postman C) Swagger / OpenAPI
A) API testing and documentation B) Designing API schemas C) Creating documentation websites
A) Swagger and OpenAPI B) RAML and API Blueprint C) Redoc and MkDocs
A) Postman B) Redoc C) Sphinx
A) parameters B) message C) status
A) daily.feels_like B) daily.temp.min C) daily.temp.max
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) Duplicating critical components B) Checkpointing and rollback in databases, retry logic C) Using parity bits to detect errors
A) Using binary search instead of linear search for large datasets B) Using linear search instead of binary search B. Using binary search instead of linear search for larg C) Adding more servers
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 use multithreading B) To avoid memory leaks C) To identify performance bottlenecks using tools
A) Caching & Memoization B) Resource Management C) Caching & Memoization
A) Avoiding memory leaks and releasing unused objects B) Testing edge cases C) Handling exceptions
A) Parallelism & Concurrency B) Algorithmic Optimization C) Database Optimization
A) Exception handling B) Caching all data C) Indexing, query optimization, and normalization/denormalization trade-offs
A) Testing after full integration B) Testing only the user interface C) Testing individual units of code (functions, classes, methods) in isolation
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 recover from failures automatically C) Ability to use resources optimallyWhich practice involves never trusting user input and checking ranges, types, and formats?
A) Input Validation B) Exception Handling C) Fail-Safe Defaults
A) Using try/except blocks B) Testing minimum, maximum, and out-of-range values C) Testing only valid inputs
A) loops B) try/except C) if/else
A) Allowing any input without checks B) Showing technical errors to users C) Defaulting to secure/safe behavior if inputs are invalid
A) Anticipating and guarding against potential failures B) Writing complex code to prevent errors C) Avoiding any error handling
A) To log runtime information B) To retry failed operations C) To define preconditions, postconditions, and invariants
A) Ignoring failed operations B) Automatically retrying operations like API calls if they fail C) Stopping the system on failure
A) To prevent errors from happening B) To collect runtime information for debugging and failure analysis C) To speed up the code
A) Manually fixing errors B) Ignoring failures C) Implementing watchdogs or self-healing services
A) pytest B) Jest C) JUnit
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 |