FREE: SCEA 5 Beta Certification Exam (Three Parts) Are you an architect who is responsible for architecting and designing
Java Platform, Enterprise Edition compliant applications, which are scalable, flexible, and highly secure? If so, this is your opportunity to get involved in the creation of the Enterprise Architect certification exam!!!
As a beta tester, you officially "test the test" and will be able to provide Sun with valuable comments and technical feedback about the Enterprise Architect questions, assignment and essay. The Sun beta exam counts toward official SCEA Certification!
Registration Start Date: September 26-27, 2007 Multiple Choice (Part I) Beta Dates: September 27 � October 22, 2007
Candidates will have four (4) hours to complete 160 questions, which should allow you time to respond to all questions and provide your valuable comments while taking the exam.
This beta exam is offered Worldwide at any Authorized Prometric Testing Centers!
Assignment (Part II) Beta Dates: November 21st - December 26th, 2007 In order to proceed to Part II you must have passed the multiple choice part. Prometric will send you an email, if you passed, on how to proceed with Part II, the assignment. You will have 25 days to complete the assignment. After you have completed the assignment, please do NOT hesitate to take Part III, the essay, to complete your beta certification.
Short Essay (Part III) Beta Dates: November 28th - December 26th, 2007 Prometric will also be sending you a voucher number for this part of the exam. It will be included in the email that will have the instructions on how to proceed with the Part II - Assignment.
Recommended Prerequisites: The Sun Certified Enterprise Architect 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
-Security
Candidates
MUST pass all three (3) parts of the beta exam in order to receive your certification kit.
BETA EXAM REGISTRATION PROCEDURE Unlike other SUN Microsystems certification exams, Part 1 (multiple choice) of this exam does NOT require a voucher. Part II (assignment) is an architecture assignment, and Part III (short essay) requires a voucher, which will be emailed to you if you pass Part I (multiple choice).
To register for the "Sun Certified Enterprise Architect for the Java Platform, Enterprise Edition 5" Beta exam, you may register online at
http://www.prometric.com/Sun/default.htm, and follow the prompts. Or, you may register by phone, by calling your regional Prometric registration office, listed at
http://www.prometric.com/ContactUs/TestTakers. Asia/Australia 61-2-96405830
Europe 31-320-239-800
Japan 81-0120-107737
Latin America Contact your local Prometric testing center, listed at
www.2test.com USA/Canada 1-800-795-3926
SCEA 5 Multiple Choice Testing Objectives "DRAFT" Section 1: Application Design Concepts and Principles
1.1Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.2Describe 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.
1.3Describe 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
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Explain appropriate and inappropriate uses for Web Services in the Java EE Platform
Section 3:Integration and Messaging
3.1Explain 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.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
Section 4: Business Tier Technologies
4.1Explain 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.
4.2Explain 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.
4.3Explain how Java EE supports the deployment of server-side components implemented as Web Services and the advantages and disadvantages of adopting such an approach.
4.4Explain the benefits of the EJB3 development model over previous EJB generations for ease of development including how the EJB container simplifies EJB development.
Section 5: Web Tier Technologies
5.1State the benefits and drawbacks of adopting a web framework in designing a Java EE application
5.2Explain standard uses for
JSP and
Servlet technologies in a typical Java EE application.
5.3Explain standard uses for
JSF technology in a typical Java EE application.
5.4Given 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
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.3Explain 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 7.1From 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.
7.2From 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.
7.3Select 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.
7.4Select 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
8.1Explain the client-side security model for the Java SE environment, including the Web Start and
applet deployment modes.
8.2Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.3Identify and classify potential threats to a system and describe how a given architecture will address the threats.
8.4Describe 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.
SCEA 5 Assignment Objectives "DRAFT" Section 1: Application Design Concepts and Principles
1.1Document a given system architecture by creating UML diagrams for it.
1.2Explain the main advantages of an object oriented approach to system design including the effect of encapsulation, inheritance, delegation, and the use of interfaces, on architectural characteristics.
1.3Describe 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.
1.4Describe 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
2.1Explain the advantages and disadvantages of two tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.2Explain the advantages and disadvantages of three tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security
2.3Explain the advantages and disadvantages of multi-tier architectures when examined under the following topics: scalability, maintainability, reliability, availability, extensibility, performance, manageability, and security.
2.4Explain the benefits and drawbacks of rich clients and browser-based clients as deployed in a typical Java EE application.
2.5Create a logical and physical model of a system infrastructure architecture
Section 3: Integration and Messaging
3.1Explain 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.
3.2Explain typical uses of Web Services and XML over HTTP as mechanisms to integrate distinct software components.
3.3Explain how Java Connector Architecture and JMS are used to integrate distinct software components as part of an overall Java EE application.
3.4Given a scenario, explain the appropriate messaging strategy to satisfy the requirements.
Section 4: Business Tier Technologies
4.1Explain 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.
4.2Explain 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.
Section 5: Web Tier Technologies
5.1Given 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
6.1Given a specified business problem, design a modular solution implemented using Java EE which solves that business problem.
6.2Given a specified business problem, identify and prioritize the main technology risk areas that must be addressed by the technical design and architecture.
6.3Explain how the Java EE platform enables service oriented architecture (SOA) -based applications.
6.4Identify how the Java SE and Java EE platform supports the internationalization and localization of applications.
6.5Explain your rationale for choosing build versus buy for a given Java EE component.
6.6Explain the typical challenges associated with the design and implementation of large scale enterprise software systems and how Java EE technology addresses those challenges.
6.7Explain 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
7.1From 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.
7.2From 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.
7.3Select 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.
7.4Select 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
8.1Given an architectural system specification, select appropriate locations for implementation of specified security features, and select suitable technologies for implementation of those features
8.2Identify and classify potential threats to a system and describe how a given architecture will address the threats.
[ September 10, 2007: Message edited by: Evelyn Cartagena-Meyer ]
[ September 10, 2007: Message edited by: Evelyn Cartagena-Meyer ]
)
