Test your basic knowledge |

SWA - Software Architecture

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






2. How many objects that a source object can legitimately reference.






3. Valid input that the program is designed to process.






4. No more than 40 hours to stop burnouts.






5. Link multiple projects together






6. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






7. Trying to access a location in memory that your computer cannot access.






8. Plan out your code.






9. Downloads without merging.






10. Ability to treat a class object as a function by overloading the () operator.






11. Makes a project compile in order of who is dependent on what






12. Bad! Don't ever use these types of variables!






13. Creates a spin-off of a repository for concurrent development.






14. Ignores files when pushing.






15. Stops when memory changes.






16. Linking to dynamic libraries is usually handled by linking to an ____________.






17. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






18. When we remove redundant or obsolete designs and replace them with a new.






19. About the interface to an object. Data contained within.






20. Breaks encapsulation boundaries.






21. Freed heap memory.






22. Helps to eliminate unnecessary "include chaining."






23. When a concrete class inherits from a pure interface.






24. When doing a - precise task.






25. Formatted code standards.






26. Code whatever it is you need to code.






27. Takes information in the index and pushes it onto the stack.






28. Meetings used to create a release plan - which will lay out the overall project.






29. Default branch within your repository.






30. When GIT cannot merge your data.






31. Variable doesn't exist.






32. Uploads changes to your current branch.






33. Weak relationship between two classes. Almost always results in a #include.






34. Adds files to the repository.






35. Separating out a section of code into a reusable function or class.






36. Functionality Tests.






37. Always do the simplest design that could possibly work.






38. What is part of the current scope.






39. Creates a copy of your current branch into a remote branch.






40. Having power over inheritance with the flexibility of composition.






41. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






42. A function that can load a library






43. Ability to withstand change and what the effects are.






44. Treating a derived class's data members like it's base class's.






45. Developers should be integrated and releasing code into the code repository every few hours.






46. Initialized stack memory.






47. A measure of logical dependency.






48. The default nickname for the remote repository.






49. Use this to find a memory address or signiture in a dll






50. Use only through the interface of the object.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests