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. Fix any problems and then repeat the process.






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






3. Helps to eliminate unnecessary "include chaining."






4. NULL memory.






5. Portioning your changes to commit by inserting them into the index.






6. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






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






9. CONSTANT






10. Function doesn't exist.






11. One of the linking methods (pragma comment)






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






13. Allows consumers to try a system earlier and give early feedback.






14. 2 Eyes + 2 Minds = AWESOME!






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






16. Ignores files when pushing.






17. The linking is already done internally






18. Simply a value.






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






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






21. When GIT cannot merge your data.






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






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






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






25. Downloads your changes and then merges.






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






27. Inheritance between object.






28. Classes build off of each other.






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






30. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






31. Puts all headers into a master header.






32. No more than 40 hours to stop burnouts.






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






34. What is part of the current scope.






35. 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.






36. When doing a - precise task.






37. When a conflict is fixed.






38. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






39. Code whatever it is you need to code.






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






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






42. No man's land. Guard bytes before the after allocated heap memory.






43. Current line that is executing.






44. When a class is defined within another class.






45. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






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






47. Ask questions and obtain the details and requirements given.






48. Try to find the flaws in your code.






49. Freed heap memory.






50. Breaks encapsulation boundaries.






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