<p>I'm in the same boat as tapedDuck... :(</p>
<p>After looking back at what I answered, I'm thinking this is where I stand:</p>
<p>I answered 36 of the 40 MC and I feel pretty good about that. The worst case scenario is a 25 in my opinion, and average case probably a 29. Sooo based on the curve in 2006...</p>
<p>25 Right: 32.89 (35.11 on the FRQ needed for a 5)
29 Right: 43.28 (24.72 on the FRQ needed for a 5)</p>
<p>My guess for my frq is about 38.89, so at this point I'm thinking I'll be ok, but we'll see soon.</p>
<p>i took ab, free response...i skipped marine bio case study...but i gotta keep in mind that I took an A course...stupid of me to think that I could challenge the all mighty CB AB course....2/3 for me...MC wasnt bad though</p>
<p>I thought that the MBCS FRQ was one of the easier ones. #3 really threw me off though.</p>
<p>I completely agree Didnotfaillife. #3 was killer at the time. I remembered the question and worked it out in my head later though and I know how I would have implemented part a. What I put down was somewhat similar though, so I may get 4 or 5 on that question. As for the other three questions, they were all fairly simple, especially number 4. Number four was ridiculously easy.</p>
<p>personally, i thought the AB exam was pretty easy. i finished each section with about 20 extra minutes. anybody else who took AB think that a certain aspect of the case study was conspicuously absent from the mc and frq?</p>
<p>I found it interesting that there were no questions, or very few, about the Unbounded Env. Wasn't that one of the biggest changes in the last chapter?</p>
<p>that's true... but that's not what i was thinking about... idk if i can say it yet. i'll bring it up tomorrow</p>
<p>the thing i noticed was that there were absolutely no questions about fish. not one. my only possible explanation is that because the MBCS wasn't written in Java 5.0, and since this is the last year of this case study, they just asked questions about the parts that were easy to convert to 5.0. I think it made it easier that we didn't have to write code for a new kind of fish or anything like that</p>
<p>are we allowed to discuss the actual questions yet?</p>
<p>Yes. The questions already got released.</p>
<p>Cool! So how did you guys do #3??</p>
<h1>3 on the A or AB exam?</h1>
<p>what was the question?</p>
<p>I think #3 on the AB was about the map with <person, priorityqueue<pair="">></person,></p>
<p>I did it, but it took a while. I made a ListIterator during a loop that used a ListIterator. It sucked.</p>
<p>I used two nested for-each loops, one to go through every person, the other to put every possible match within the mapping for that person. The great thing about those loops is that, unlike with iterators, they won't cause a ConcurrentModificationError</p>
<p>Argh, never mind. Number 3 was about initializing the tree-game-thing. I made a recursive method that returned a TreeNode. It seemed pretty simple, though I made it more complicated than it needed to be.</p>
<p>To One: I don't think you would get a concurrent modification error as long as you were not, well, modifying the list. The List of Persons wasn't being modified by the iterator, the Map was.</p>
<p>I did #3 by adding the TreeNodes to a queue after they were instantiated. It was something like.</p>
<p>root = new TreeNode with the value
queue.add(root);
while(queue isn't empty and queue size does not equal 2^(numLevels - 1))
{
take the first item in the queue
add two children
add the two children to the queue
}</p>
<p>If that's too much information about the question delete this post - I don't know how much i can say while complying with the rules and I don't want to lose my scores.</p>
<p>for the tree-game thing, i the only command in my constructor was a call to a recursive method that returned a TreeNode. For the Map<person,priorityqueue<pair>> one, I think you can use one for-each loop, but you need an iterator inside it, not another for-each. i dont remember the specifics of the question, so i dont remember exactly why.</person,priorityqueue<pair></p>
<p>A for-each loop is essentially the same thing as the iterator, except Java 5.0 hides it. So it is basically as you said, an iterator within the loop (some people confuse the for-each loop with the plain-old for loop)</p>