|
Product Description
This exam is for enterprise architects responsible for architecting and designing Java Platform, Enterprise Edition technology-compliant applications, which are scalable, flexible, and highly secure. This exam is designed for candidates with experience in the following areas (typically 5 or more years): Application design: concepts and principles, Common architectures, Integration and messaging, Business-tier technologies, Web-tier technologies, Java EE technology, Patterns and Security. If a candidate has NOT taken the SCEA 5 certification exam, Sun recommends the candidate take the new SCEA 5 certification exam. If a candidate has taken and passed all three steps to the SCEA (CX-310-051/CX-310-300A,CX-310-052), Sun recommends that the candidate take the SCEA 5 Upgrade exam.The upgrade exam is for candidates who have successfully been certified on a prior version of the SCEA.
Assignments purchased on the Web site may only be used in the US. If you reside outside the US please select a country to inquire about products delivered in your country.
Details
- Delivered at: Authorized Worldwide Prometric Testing Centers
- Prerequisites: Passed (CX-310-051/CX-310-300A,CX-310-052)
- Other exams/assignments required for this certification: None
- Exam type: Multiple choice and drag and drop
- Number of questions: 48
- Pass score: 70% (29 of 48 questions)
- Time limit: 120 minutes
Back to top
Languages
English
Back to top
Assignment Objectives
Section 1: Application Design Concepts and Principles
- Describe how the principle of "separation of concerns" has been applied to the main system tiers of a Java EE application. Tiers include client (both GUI and web), web (web container), business (EJB container), integration, and resource tiers.
- Describe how the principle of "separation of concerns" has been applied to the layers of a Java EE application. Layers include application, virtual platform (component APIs), application infrastructure (containers), enterprise services (operating system and virtualization), compute and storage, and the networking infrastructure layers.
Section 2: Common Architectures
- Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
- Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
- Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
- Explain appropriate and inappropriate uses for web services in the Java EE Platform.
Section 3: Integration and Messaging
- Explain possible approaches for communicating with an external system from a Java EE-based system given an outline description of those systems and outline the benefits and drawbacks of each approach.
- Explain typical uses of web services and XML over HTTP as mechanisms to integrate distinct software components.
Section 4: Business Tier Technologies
- Explain and contrast uses for entity beans, entity classes, stateful and stateless session beans, and message-driven beans and understand the advantages and disadvantages of each type.
- Explain and contrast the following persistence strategies: Container-managed persistence (CMP) BMP, JDO, JPA, ORM, and using DAOs (Data Access Objects) and direct JDBC-based persistence under the following headings: ease of development, performance, scalability, extensibility and security.
- Explain how Java EE supports the deployment of server-side components implemented as Web Services and the advantages and disadvantages of adopting such an approach.
- Explain the benefits of the EJB 3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.
Section 5: Web Tier Technologies
- State the benefits and drawbacks of adopting a web framework in designing a Java EE application
- Given a system requirements definition, explain and justify your rationale for choosing a web-centric or EJB-centric implementation to solve the requirements. Web-centric means that you are providing a solution that does not use EJBs. EJB-centric solution will require an application server that supports EJBs.
Section 6: Applicability of Java EE Technology
- Given a specified business problem, design a modular solution implemented using Java EE, which solves that business problem.
- Explain how the Java EE platform enables service-oriented architecture (SOA) -based applications.
- Explain how you would design a Java EE application to repeatedly measure critical non-functional requirements and outline a standard process with specific strategies to refactor that application to improve on the results of the measurements.
Section 7: Patterns
- From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition and named using the names given in that book.
- From a list, select the most appropriate pattern for a given scenario. Patterns are limited to those documented in the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software and are named using the names given in that book.
- Select from a list the benefits and drawbacks of a pattern drawn from the book - Gamma, Erich; Richard Helm, Ralph Johnson, and John Vlissides (1995). Design Patterns: Elements of Reusable Object-Oriented Software.
- Select from a list the benefits and drawbacks of a specified Core J2EE pattern drawn from the book – Alur, Crupi and Malks (2003). Core J2EE Patterns: Best Practices and Design Strategies 2nd Edition.
Section 8: Security
- Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
- Identify and classify potential threats to a system and describe how a given architecture will address the threats.
- Describe the commonly used declarative and programmatic methods used to secure applications built on the Java EE platform, for example use of deployment descriptors and JAAS.
Back to top
|
|
