If, by reading all of the material and going through all of the exercises you have thus far, you are preparing to write a test... congratulations, you're probably finished learning what you need to know. If you're preparing to get a job, you have some work ahead of you. I've been writing software professionally since 1997 (not as long as some, but long enough to impart *some* knowledge.) The more time you spend trying to solve real problems by writing software, the better you will become at doing just that. Having knowledge of an API, system, class library or a language's syntax will never compare to actually doing something useful with that language.
When you get out of school you'll end up running into languages you've never worked with before, didn't spend any time learning and you will be able to pick up their syntax in a very short period of time (for me, recently, it's within hours.) Learning the gotchas of each language/platform combination can take a very long time. Learning how not to shoot yourself in the foot in those languages can take even longer. If I were you, I would create a project for yourself, define a list of requirements. Then, go through the list of requirements and attach an hourly amount to each one, your estimate of how long you think it will take you to perform those tasks. Then, perform them. Don't necessarily focus on making sure you stay within the time you set for yourself, just focus on providing the best solution per task that you know how.
Your first self-made project might go over the hourly allotment, it may not, but either way you'll be well on your way. The next self-made project you assign yourself should be longer, more complex and involve more features (perhaps additions to the project you assigned yourself the first time.) Practice makes perfect. Also, do your best to try not to be "creative" necessarily, solve the problem, don't try to be a code hero, and you should do fine from there.