I am just the French guy, here, but isn't this a simple grammar error in this sentence Which functionality is used for Marketo embedded forms?
If it was simply written "Which functionality could be used on the Marketo embedded form?" or something similar, the answer C would seem more natural wouldn't it?
It would still be wrong because "ReCAPTCHA" and "Suppress competitors" can both be used on embedded forms exactly as they can be on Marketo LPs. They aren't built-in features in either case, but they're equally doable.
I really, really hate poorly QA'd tests. We see it in big-name regulatory compliance certs as well. People don't like to put their best + brightest in charge of writing tests because it's "beneath their pay grade" but that's a bad move.
The funny thing (and again, that it probably because, as a foreigner, I probably miss some nuances) I would not have failed that question. Mainly because, in the context of the test (that focuses on Marketo out of the box functionality), only the answer C is possible. B is simply not possible and A and D are not OOB. But I agree it's more reasoning by the absurd.
Ayana Nickerson I don't know how this one would have gotten through. PP (which was my part of the test) isn't something that embedded forms can support really since they can't read the Marketo cookie to identify the lead (unless iFramed in via a page.) I wouldn't have written the question as such regardless. It looks like this somehow got the question and answer switched up.
None of these answers are possible with an embedded form on a non-marketo landing page.
Lynn Ray Magers-Pardo wrote:
It's this question where the correct answer-Lightbox- is not within the multiple choice options.
"A marketer wants to launch a new gated asset on a company website using a Marketo embedded form. Which functionality is used for Marketo embedded forms?
B. Form Pre-fill
C. Progressive Profiling
D. Suppress Competitor form fills
Answer is C
Reference: http://docs.marketo.com/display/public/DOCS/Use+a+Form+in+a+Lightbox "
Fortunately, for review purposes, the reference URL is correct but it doesn't bode well for test questions.
(I did send a note to MKTO re: this.)
Thank you for your feedback,
Progressive Profiling works with embedded forms on non-Marketo LPs. Progressive Profiling/Form Prefill on Embedded form
Robb, like Dan said, ProgPro works on non-Marketo LPs. ProgPro doesn't read data out of the cookie value (neither does Pre-Fill, for that matter -- they use the cookie as the key for a database lookup, but the cookie is just a unique id).
With ProgPro, the db lookup merely needs to tell the forms lib whether a field has *a* value or not, not what that value is. As such, it can function across all domains that share an associated Munchkin cookie.
Thank you so much for your feedback regarding the sample questions. Did you post the sample question you had concerns about?
Thanks so much.
It's 7 replies above yours (in large font): A marketer wants to launch a new gated asset on a company website using a Marketo embedded form...
Just took the new exam today (first year certification) after studying for the old version for almost three months - I thought it was hard.
While the spelling and general formatting of the questions have drastically improved from the old practice test, I would not say that "gotcha!" wording has been totally removed. I found the sample questions from the training to be fairly straightforward, but the actual test had reworded versions that shifted focus of the question or asked for different information, sometimes awkwardly. There were also questions that (as far as I remember) were not mentioned in the training, sample questions, or recommended reads for either test version - marketing topics like creating a scoring plan, for example.
The challenge with the Old test wasn't just memorization, but I encountered several "MCE" people who really had no idea how to build a whitepaper program in Marketo. So the new test that many of us helped add questions to, was designed to ask meaningful "work related questions." There were plenty of variations on similar situations because we wanted to have people who could be that flexible.
I am also unhappy with certain aspects of the test creation process that you are now seeing in how some questions are worded. It's pretty hard to build a "fair" test.