A) Only the source code of the software B) Written text and illustrations describing architecture, design, functionality, and usage C) Helps new team members onboard quickly
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) 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) Doxygen B) Javadoc C) Confluence
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) Apache License 2.0 C) MIT License
A) MIT License B) Creative Commons C) Apache License 2.0
A) Media and documents, not software B) Software only C) Hardware designs
A) It is not necessary for open-source projects B) It protects intellectual property and clarifies usage rights C) It makes the software harder to use
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) Redundancy B) Error Detection & Correction C) Recovery Mechanisms
A) Automated testing B) Redundancy C) Check sums, parity bits, and validation rules
A) Automated testing B) User acceptance testing C) Performance testing
A) Duplicating servers B) Checkpointing and rollback in databases C) Using parity bits
A) To increase the number of tools used B) To avoid following any conventions 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) Postman B) Redoc C) Sphinx
A) parameters B) message C) status
A) daily.temp.min B) daily.temp.max C) daily.feels_like
A) Ability to duplicate critical components B) Optimal use of resources (time, memory, CPU) while delivering results quickly 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) Adding more servers B) Using linear search instead of binary search B. Using binary search instead of linear search for larg C) Using binary search instead of linear search for large datasets
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) Database Optimization B) Algorithmic Optimization C) Caching & Memoization
A) To identify performance bottlenecks using tools B) To avoid memory leaks C) To use multithreading
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) Testing only once before release B) Working on code in isolation without sharing C) Frequently integrating code into a shared repository and running automated tests
A) To ensure new code does not break existing functionality B) To delay integration until the end C) To reduce the number of tests
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) Exception Handling B) Fail-Safe Defaults C) Input Validation
A) Testing minimum, maximum, and out-of-range values B) Testing only valid inputs C) Using try/except blocks
A) try/except B) loops C) if/else
A) Showing technical errors to users B) Defaulting to secure/safe behavior if inputs are invalid C) Allowing any input without checks
A) Avoiding any error handling B) Anticipating and guarding against potential failures C) Writing complex code to prevent errors
A) To log runtime information B) To define preconditions, postconditions, and invariants 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 speed up the code B) To collect runtime information for debugging and failure analysis C) To prevent errors from happening
A) Manually fixing errors B) Ignoring failures C) Implementing watchdogs or self-healing services
A) JUnit B) Jest C) pytest
A) Code that does not have any error handling B) Code that only works with perfect inputs C) A login form that handles incorrect passwords gracefully without crashing |