Q: 20
An App Builder at UVC would like to prevent users from creating new records on an Account related
list by overriding standard buttons. Which two should the App Builder consider before overriding
standard buttons?
Options
Discussion
B C for sure. Both let you control button behavior or visibility without custom coding every scenario.
B and C tbh. You can definitely override a standard button like "New" with a Visualforce page, so that's B. Also, even if you can't override a button, you can still hide it on the page layout so users won't see it (that's C). A isn't really about overrides and D is misleading because you can't always relocate or relabel buttons. Anyone see it differently?
Maybe D, since I remember hearing you can move or relabel buttons on the page. Not 100 percent sure but seems right.
B/C? I've seen similar on practice tests. Official guide and Salesforce help docs cover button overrides and page layout options pretty well.
Be respectful. No spam.
