You can use a mock design by all means but I HIGHLY recommend submitting a sanitized actual design. This gives the added benefit of already having been defended once (in front of a customer) and will be driven by real world scenarios. This will make the defense process go much more smoothly as they inquire why some decsions were made versus others, etc. These will be questions you've already addressed (consider the actual presentation to customers as a rehearsal!)
When using a mock design, the tendency might be to push things too far and get lost in the details. I conteplated doing this but thought better of it as I suspected I would paint myself into a corner without the usual layer 8 stuff to keep me in check.
Regarding what it looks like:
The framework doesn't have to follow the VAC services kit 100% but it does need to be able to provide the high level design, buildout plans, etc.
John Arrasjid sums it up nicely:
"Design documents do not have to be based on VMware deliverables but
must meet content coverage. Blueprints & app provide detail."
Really, if its a solid design it doesn't matter if it fits VMware's framework or something home grown. If you look at a lot of VMware centric services organizations, you'll see that they all kind of take roughly the same things into consideration.
I can't share the details of the application but when you pass your design exam you'll see it's pretty straightforward.
