Evaluate an Application Design and Implementation Considering Maintainability 350-901 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A team maintains a large Python library for network automation. The library has extensive docstrings and a README, but new team members still struggle to understand how to combine different modules to accomplish common tasks. The code review process does not catch this issue. Which documentation improvement would most directly address this onboarding problem?

   • ACreate a separate wiki page for each module with a list of its functions.
   • BIncrease the number of comments in the code to explain each line.
   • CAdd usage examples and tutorials to the documentation that show how to combine modules for common workflows.
   • DRequire all functions to have a docstring with a formal specification.
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A developer submits a pull request that adds a new feature to a network configuration tool. The code is functional but has several large functions with many parameters and inconsistent naming. The team wants to use code review to improve maintainability. What is the most effective review focus?

   • AOnly check that the code compiles and passes existing tests.
   • BApprove the pull request immediately to keep the development velocity high.
   • CFocus exclusively on the performance of the new feature in a production-like environment.
   • DEvaluate the code for adherence to the team's style guide and suggest splitting large functions into smaller, single-purpose ones.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   What is the primary purpose of documentation and comments in supporting maintainability?

   • ATo replace the need for writing clean code
   • BTo make the code run faster
   • CTo increase the file size of the source code
   • DTo explain why certain design decisions were made and how to use the code
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A team uses a code review process, but reviews are often superficial, focusing on style rather than logic. As a result, bugs are found in production. The team wants to improve the effectiveness of code reviews. Which change is most likely to improve review quality?

   • ALimit the number of reviewers to one person to reduce conflicting opinions.
   • BUse a linter to automatically check for style issues.
   • CRequire all reviews to be completed within 24 hours to speed up the process.
   • DCreate a review checklist that includes specific checks for error handling, edge cases, and test coverage.
   Reveal Solution Discussion Select an answer first
6. 5foundation · easy

   Which type of comment is most valuable for maintainability?

   • AComments that restate what the code does line by line
   • BComments that explain the 'why' behind non-obvious code
   • CComments that are automatically generated from method names
   • DComments that are only added after the code is complete
   Reveal Solution Discussion Select an answer first