問題文
A railway operator's Visualforce timetable page fails to save with a message about the view state being too large. Before changing anything, the developer wants to know what the platform is actually measuring. Which items count toward that limit?
選択肢
- The state of the components on the page, the submitted field values, and the controller's members other than the ones declared as not saved, because everything the page needs to be rebuilt on the next request travels with the form.
- The rows returned by every query the controller issued during the request, whether or not the controller kept them, because the platform has to be able to rebuild the result set for the next request without querying the database again, and the size grows with it.
- The static resources the page loads plus the size of the rendered markup that the browser receives, so trimming the timetable markup is what brings the figure back under the maximum.
- The state of the components, the submitted field values, and the controller's members including the static ones, because a static member is part of the same serialized payload that travels with the request.