Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Platform Developer II Topic 3 Question 101 Discussion

Actual exam question for Salesforce's Platform Developer II exam
Question #: 101
Topic #: 3
[All Platform Developer II Questions]

Refer to the exhibit

Users of this Visualforce page complain that the page does a full refresh every time the Search button Is pressed.

What should the developer do to ensure that a partial refresh Is made so that only the section identified with opportunity List is re-drawn on the screen?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Cecily
2 months ago
Option B with the render attribute? That's a classic developer trick to show off, but I'm not sure it's the right solution for this problem. Keep it simple, folks - go with A!
upvoted 0 times
Kami
1 months ago
Yeah, let's go with option A for a partial refresh.
upvoted 0 times
...
Ashton
1 months ago
I think option B might be overcomplicating things, A seems like the better choice.
upvoted 0 times
...
Kenneth
1 months ago
I agree, keeping it simple with option A is the way to go.
upvoted 0 times
...
...
Mike
2 months ago
Whoa, hold up, are we sure the developer didn't just forget to include the 'required' attribute on the 'Search' button? That would be a real knee-slapper of a solution!
upvoted 0 times
...
Alisha
2 months ago
I'd steer clear of option C. Returning null from the action method? That just sounds like a recipe for trouble. A or D are my top picks here.
upvoted 0 times
Jutta
1 months ago
Yeah, option D could also work to ensure a partial refresh.
upvoted 0 times
...
Aileen
2 months ago
D) Implement the tag with immediate = true.
upvoted 0 times
...
Ivette
2 months ago
I agree, option A seems like the best choice to avoid a full refresh.
upvoted 0 times
...
Peggie
2 months ago
A) Enclose the DATA table within the tag.
upvoted 0 times
...
...
Ashleigh
2 months ago
Hmm, that makes sense too. Let's see what others think before we make our final choice.
upvoted 0 times
...
Aide
2 months ago
I disagree, I believe the correct answer is D) Implement the tag with immediate = true.
upvoted 0 times
...
Mignon
3 months ago
Option D looks interesting, but I'm not sure about that 'immediate = true' part. Might be worth a try, but A sounds like the safer bet to me.
upvoted 0 times
Beth
1 months ago
Let's go with A then, it's the most reliable option to ensure a partial refresh.
upvoted 0 times
...
Leana
2 months ago
I agree, A seems like the best choice to avoid a full refresh every time the Search button is pressed.
upvoted 0 times
...
Leslie
2 months ago
I think A is the safer option here. It will ensure only the section identified with opportunity List is re-drawn.
upvoted 0 times
...
...
Jean
3 months ago
Definitely go with option A. Enclosing the DATA table within the tag is the way to go. Partial refreshes are the way to keep users happy and avoid those annoying full-page reloads.
upvoted 0 times
Antonio
2 months ago
Let's go with option A then, to avoid full-page reloads.
upvoted 0 times
...
Frederick
2 months ago
I agree, partial refreshes are much better for user experience.
upvoted 0 times
...
Ruby
2 months ago
Yeah, enclosing the DATA table within the tag will solve the issue.
upvoted 0 times
...
Ngoc
2 months ago
I think option A is the best choice.
upvoted 0 times
...
...
Ashleigh
3 months ago
I think the answer is A) Enclose the DATA table within the tag.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77