True, it's not just about the manual.
For example, to be a certified java programmer, besides knowing language basics/syntaxt, you also have to understand threading concepts (how to create threads/manage, how deadlocks might occur ...).

SUN CERTIFIED DEVELOPER FOR JAVA 2 PLATFORM
(Objectives cover Step 1 and Step 2 of the certification.)

• Write an application program using Java technology. The application requires the following:
  1. A graphical user interface demonstrating good principles of design
  2. A network connection, using a specified protocol, to connect to an information server
  3. A network server, which connects to a previously specified Java technology database
  4. A database, created by extending the functionality of a previously written piece of code, for which only limited documentation is available
• List some of the major choices you must make during the implementation of the above.
• List some of the main advantages and disadvantages of each of your choices.
• Briefly justify your choices in terms of the comparison of design and implementation objectives with the advantages and disadvantages of each.

Perl could have the same thing -- certification ain't just about memorizing the manual, but you sure as heck need to how my/local/our works.

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.