Answer: A. <apex:page standardController="Notice__c" extensions="myControllerExtension">

This is the same question you asked last Tuesday, with the same options. The page uses the custom object’s standard controller (standardController) and attaches the extension class with extensions. For a custom object, the standard controller name is its API name, ending in __c. Your option shows Notice_c, which is an OCR slip for Notice__c.

xml
<apex:page standardController="Notice__c" extensions="myControllerExtension">
<apex:form>
<apex:inputField value="{!Notice__c.Name}"/>
<apex:commandButton action="{!save}" value="Save"/>
</apex:form>
</apex:page>

As we discussed after that question, “standard” in standardController means the controller is provided by Salesforce, not that the object has to be a standard object. Every custom object gets one automatically.

The other options don’t fit:

B. controllers="...": There is no controllers attribute on <apex:page>.
C. apex:pege=Notice extends=...: This isn’t valid Visualforce syntax. The attribute is extensions, not extends, and attributes use name="value" pairs.
D. controller="Notice__c": The controller attribute names a custom Apex controller class. Notice__c is an object, so it needs standardController....