This has long been a requested fix...and as you no doubt already know, the formatting of question slides can give you less than ideal results as it relates to the "undersized" text boxes that appear once you get done setting up your question slides.
 
Additionally, as I'm sure you've already experienced, resizing the text box elements makes things look worse visually, and heaven help you if you attempt to ungroup the question elements!!!
 
And honestly, I got this idea from asm0d on the Adobe Breeze Forums, so I want to make sure that credit is given where credit is due.
 
The *only* thing left to do is to manually edit the question elements and "fake it" in terms of getting the text boxes to expand on your slides.  The downside of what I'm about to explain, however, does introduce another potentially nasty artifact: namely, that you will lose some level of data reporting back to the LMS.
 
If that hasn't scared you yet, good!  It's not all that terrible, but there are prices to pay when trying to trick Presenter into doing things it's not capable of handling on its own.
 
Enough chat....here's the "fix":
 
1) Create your quiz and question slide as you normally would
 
2) When you return back to your deck, go to one of your question slides.  What you want to do next is edit away any content within the text boxes for the individual question elements.  Let me be VERY clear about this: you're NOT killing off the checkboxes or radio buttons for the questions...you're merely going to eliminate all of the text that appears as part of the question elements.  What you'll end up with are "blank" radio buttons or checkboxes (depending on the type of question(s) you created)
 
3) Now you can create your own text boxes with whatever content you need to display.
 
Now, here's the problem with this strategy...
 
Even though Presenter will still track scores, if you try to call up grades by answers, everything is going to be blank...afterall, you eliminated the text from the question elements!  Of course, if your only concern is using the questions as a way to check the learner's knowledge (i.e., unevaluated scoring), then you've got no problem.  Even if you are looking for graded scores, you could still be okay if all you need to do is track which questions they got wrong.  The real big issue, however, is if you need to track the individual question with their associated values.
 
Hope that helps!
 
Rob

My pleasure Lisa!  And Happy Holidays to you too!!!!
 
And by the way...I was helping out another Presenter user, and these ideas got batted around a little:  
 
Rather than delete any of the text associated with the radio and checkboxes that appear, you *could* opt to change the text and use the same color as your presentation's background.  Then all you'd need to do is add new text boxes for each of the questions that appears on your slide.  The big problem with this, however, is that if you need to modify the content at all, you'll have to recolor your text all over again the moment you exit out of the Quiz Manager.  Yuck!
 
Solution workaround #2: cover all the question/answer text with one HUGE rectangle, using the same color as your presentation's background.  Result: you'll end up being able to use the question text as entered into the Quiz Manager, BUT you have the added flexibility to customize the layout of your "manually created" text boxes as you see fit.  This is a FAR EASIER thing to do, and regardless of whatever editing/updating you need to do to the base question text, the rectangle that sits on top of everything will obscure Breeze's/Presenter's question text underneath.  
 
Added Bonus: the fact that the text associated with radio buttons/checkboxes will still be intact, means that the LMS reports you can access from your server will have more meaning as you go through your reports.
 
However, there is a caveat: the above assumes that you have a solid color background.  In most cases, this shouldn't be a problem, but I've already worked on presentations that have been heavily treated with a variety of design elements, including gradient backgrounds.  This sort of thing will no doubt make the above workaround(s) more difficult to achieve.
 
Rob