Which two should the App Builder consider before overriding standard buttons?

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?
A . Standard buttons can be changed on lookup dialogs, list views, and search result layouts
B . Standard buttons can be overridden with a Visualforce page
C . Standard buttons that are not available for overrides can still be hidden on page layouts
D . Standard buttons can be overridden, relocated on the detail page, and relabeled

Answer: B, C

Explanation:

Standard buttons can be overridden with a Visualforce page to provide custom functionality or user interface. For example, you can override the New button on an object to display a custom Visualforce page instead of the standard page layout3. Standard buttons that are not available for overrides can still be hidden on page layouts to prevent users from accessing them. For example, you can hide the Delete button on an object to prevent users from deleting records