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. When a concrete class inherits from a pure interface.






2. One of the linking methods (pragma comment)






3. Connection between a local brand and a remote branch.






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






5. Meetings at the beginning of each iteration to produce a plan of programming tasks.






6. Breaks encapsulation boundaries.






7. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






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






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






11. Variable doesn't exist.






12. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






13. Ability to accept different types of parameters to bind to different implementations at run-time.






14. Views all previous changes.






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






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






17. When GIT cannot merge your data.






18. Inheritance between object.






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






20. Downloads without merging.






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






22. Concept based on limiting the scope of modules to provide better structures.






23. Formatted code standards.






24. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






25. Copies all changes from one branch into another branch.






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






27. The process of deciding which function definition to link during run-time.






28. STOP!!






29. Current line that is executing.






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






31. Makes a copy of your repository.






32. Static in C++. Can span all instances of a class.






33. Fix any problems and then repeat the process.






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






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






36. Invalid or unexpected input that the program is not designed to process.






37. The linking is already done internally






38. Removes files from the repository.






39. When you type in an object - you can see its attributes.






40. Figure out what is feasible. Decide whether to use API's or to write from scratch.






41. Plan out your code.






42. Written by the customers as things that the system needs to do for them.






43. You have to tell it to link






44. Adds files to the repository.






45. NULL memory.






46. Helps to eliminate unnecessary "include chaining."






47. Stand up meetings show who will be valuable and needed.






48. Puts all headers into a master header.






49. When doing a - precise task.






50. Code generation in a lib






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