Test your basic knowledge |

Enterprise Application Structure Patterns

Subject : it-skills
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. A view that proceses domain data element by element and transforms it into HTML.






2. An object that encapsulates access to an external system or resource.






3. A structure to organize database mappers that handle inheritance hierarchies.






4. Has one class perform the database mapping for a child class.






5. A centralized point for handling screen navigation and the flow of an application.






6. Keeps the session state on a server system in a serialized form.






7. An object that represents a database query.






8. An in-memory representation of tabular data.






9. Links classes during configuration rather than compilation.






10. Prevents conflicts between concurrent business transactions by allowing only one business transaction at a time to access data.






11. Stores session data as commited data in the database.






12. An object that wraps a row in a database table or view - encapsulates the database access and adds domain logic on that data.






13. An object that carries data between processes in order to reduce the number of method calls.






14. A single instance that handles the business logic for all rows in a database table or view.






15. A well-known object that other objects can use to find common objects and services.






16. Splits user interface interaction into three distinct roles.






17. A controller that handles all requests for a Web site.






18. An object that doesn't contain all of the data you need but knows how to get it.






19. Maintains a list of objects affected by a business transaction and coordiantes the writing out of changes and the resolution of concurrency problems.






20. A layer of Mappers that moves data between objects and a database while keeping them independent of each other and the mapper itself.






21. Defines an application's boundary with a layer of services that establishes a set of available operations and coordinates the application's response in each operation.






22. Saves a graph of objects by serializing them into a single large object (LOB) which stores it in a database field.






23. Removes dependence upon problematic services during testing.






24. Saves the database ID field in an object to maintain identity between an in-memory object and a database row.






25. Represents an inheritance hierarchy of classes with one table for each class.






26. Mediates between the domain and data mapping layers using a collection-like interfacefor accessing domain objects.






27. A type that acts as the supertype for all types in its layer.






28. Represents a monetary value.






29. An object that handles a request for a specific page or action on a Web site.






30. Defines an interface in a seperate package from its implementation.






31. An object that sets up a communication between two independent objects.






32. Saves an association as a table with foreign keys to the tables that are linked by the association.






33. An object that acts as a Gateway to a database table. One instance handles all the rows in the table.






34. Organizes business logic by procedures where each procedure handles a single request from the presentation.






35. Maps an association between objects to a foreign key reference between tables.






36. Represents an inheritance hierarchy of classes with one table per concrete class in the hierarchy.






37. Represents an inheritance hierarchy of classes as a single table that has columns for all the fields of the various classes.






38. An object that acts as a Gateway to a single record in a data source. There is one instance per row.






39. An object model of the domain that incorporates both behavior and data.






40. Stores session state on the client.






41. A subclass that provides special behavior for particular cases.






42. Ensures that each object gets loaded only once by keeping every loaded object in a map. Looks up objects using the map when referring to them.






43. Prevents conflicts between concurrent business transactions by detecting a conflict and rolling back the transaction.






44. Provides a coarse-grained facade on fine-grained objects to improve efficiency over a network.






45. Maps an object into several fields of another object's table.






46. Locks a set of related objects with a single lock.






47. A small simple object - like money or a date range - whose equality isn't based on identity.






48. Turns domain data into HTML in two steps: first by forming some kind of logical page - then rendering the logical page into HTML.






49. An object that sets up a communication between two independent objects.






50. Renders information into HTML by embedding markers in an HTML page.