Can you please repost the link.

However, it’s not that bad if you know your .NET framework and you’ve done a couple of EPiServer projects. A lot of questions can be guessed correctly just by asking yourself how you would implement something if you were following standard .NET design patterns.

Make sure you go through all the questions before you answer any of them – as Jon Marks has pointed out, some questions later on in the test can give you clues to earlier questions…

My advice: Do not answer any of the questions you know the answer to if they contain code samples. You’ll be overjoyed to come back to them later! Come back to them at the end and answer them once you’ve sure you won’t get any use from them.

I just took the CMS5 test, failed with 1% margin – I’ll admit I’ve only been developing in EPiServer for about six months, sure some of the questions are valid knowledge you should know from the top of your head.

… but, a lot of the questions are horribly designed such as the page.ACL.QueryAccess()-question and it’s siblings where you have four methodcalls/class names/property names which all look very much alike and have to pick the correct one and in all honesty the reason I use VisualStudio to develop is so I dont have to remember stupid things like that and can focus on the implementation details of my application instead of having to remember parameter orders and class/method names, sigh.

And the fact that there are no clear instructions on what to study for the test is even worse, coupled with the fact that detials are sprinkled among episerverworld-blogs, the sdk and tech notes… well, yeah.

I took the three day course in “EPiServer” with you in November 2008, and tried to become a ‘EPiServer Ceritified Developer’ the last day of the course. I did not pass.

But yesterday I took the test again and passed =), many thanks for writing about important things to study.. that helped me alot.

We still have a bunch of developers that are going to take the test, so I wanted to give them some idea of what to study.

I think the test was good in a way that you will have a really hard time to pass if you don’t have enough experience with EPiServer. It’s a measurement that you actually know the framework and it gives the certificate a higher creadability.

I wonder though how many developers that actually use the workflow foundation functionality in EPiServer and if it really should be in the test. But I guess that is why you need 60% to pass and not 75%.