|
[this section needs reformatting. It is not complete]
This document isnt written so that anyone who reads it can
pass the exam with no further study, but rather to highlight the
kinds of things which Sun expect you to know. The objectives given
for the Architect exam on Suns Web site are very vague, and
it is difficult for people to gain sufficient confidence to sit
the exam when it is so unclear precisely what material needs to
be covered. Hopefully this document will help a little.
In addition to background reading on any of the technologies mentioned
above, I would particularly recommend:
Learning about RMI architecture and features
Learning about CORBA architecture and features
Learning about EJB architecture and features (probably a good idea
to read about JavaBeans first!)
Learning about JDBC architecture (and its relationship with SQL).
Learn a little about OODBMSs and OQL.
Whitepapers available via Suns Web site should be quite a
help with this.
Subjects included a lot of EJB, A reasonable amount, but easy level
of UML what methods were called by what in the sequence diagrams,
what the relationship between classes and interfaces were in class
diagrams. Patterns were covered as much as UML. There were no questions
that asked you to name a pattern from UML despite the objectives.
2) Know UML diagrams reasonably well. I'd say this means knowing
the difference between the generalization and realization symbols
- stuff like that. UML Distilled by Fowler should suffice.
3) Know your patterns! Know all the pattern names, know what they
are used for, and know how parts of J2EE use patterns. The Design
Patterns book will give you most of this.
4) Know the details of the protocols mentioned in the objectives.
Know what they do, what they are good/bad for, their mechanics,
how they interact with firewalls (where is that mentioned in the
objectives?).
5) Know the details of Applet related security.
6) For questions with multiple answers the test tells you how many
correct answers there are. This made things much easier.
7) There are some things that are obvious holdovers from the old
test. Not too many but I was a little surprised.
8) There are a few strangely/badly worded questions on the test.
Don't let them rattle you. I think Sun needs to do another pass
at editing the questions.
The first five questions are about design patterns including proxy,
iterator, observer, faccade.
There are two questions about internalization.
One question about applet security.
There are many questions about common architecture and ejb application.
Sun gives a lengthy scenerio and asks you to pick the appropriate
ones.
At least 3 questions have up to 7 answer options. It is really
time comsuming to read scenerio and analyze the answer options,
especially when the options are not easy to pick, and I have go
through the process of elimination. When I see these lengthy questions,
I mark them to answer later. First, because these questions are
time comsuming. Second, other short questions may refresh my overall
memory about j2ee and provide info to select the corrects answers
(or eliminate the wrong answers).
There are about 4 questions about UML where a exhibiting diagram
is given and asking for the association, generalization, mupliplicity.
About 3 questions about protocols such as communicate between emulator
applet to terminal server through firewall (only port number 80
and 433 are allowed through fire wall).
I remember there are 2 answer options about DNA load balancing
( I don't know how DNA fit to J2EE architect. I know J2EE architect
have many advanges over DNA (Microsoft Distributed interNetwork
Architect).
About 3 questions about scalability, manability,etc..
A must readme file:Guide to SCEEJ2EE.html(from
http://groups.yahoo.com/group/scea_j2ee/files/)
Must read List:
http://www.hjug.org/architect.html
go to http://groups.yahoo.com/group/scea_j2ee/files/
Find
1. John's note (java ranch).
2. Chris 's note (SCEA quick reference)
3. All the PDF file from PDF directory Must Must read
(http://groups.yahoo.com/group/scea_j2ee/files/SCEA-Nutshell/
http://groups.yahoo.com/group/scea_j2ee/files/Balaji%20Notes/
(I add to my note with SUN SL425 training and UML and Security info
to John's note (java ranch).
With UML and design pattern
I am not only read UML distilled. But also play with all the case
with Together control Center. Use Rational XDE to learn patterns
because XDE give all the 28 patterns (class diagram and description).
4. EJB: Read at lease 5 times EJB book from O'reilly
5. JMS and I18N: Read from SUN website. The turorial (Just first
3
chapter).
6. Security: Read from Sun JDC and Java 2 Network Security from
IBM
I also read the internet security from O'reilly.
Must have mock test site:
http://ibelgique.ifrance.com/sweber/
Optional:
Read all the posting message and use proxy pattern to filter our
message, read the message that you need.
|