310-083 試験問題を無料オンラインアクセス

Which two about WAR files are true? (Choose two.)

• A.WAR files must be created by using archive tools designed specifically for that purpose.
• B.WAR files must contain the web application deployment descriptor.
• C.The web container must serve the content of any META-INF directory located in a WAR file.
• D.The web container must allow access to resources in JARs in the web application library directory.
• E.WAR files must be located in the web application library directory.

Click the Exhibit button.
Assume the product attribute does NOT yet exist in any scope.
Which two create an instance of com.example.Product and initialize the name and price properties to the name and price request parameters? (Choose two.)

• A.<jsp:useBean id="product" class="com.example.Product" />
  < jsp:setProperty name="product" property="name"
  value="${param.name}" />
  < jsp:setProperty name="product" property="price"
  value="${param.price}" />
• B.<jsp:useBean id="product" class="com.example.Product" />
  < jsp:setProperty name="product" property="*" />
• C.<jsp:useBean id="product" class="com.example.Product" />
  < % product.setName( request.getParameter( "name" ) ); %>
  < % product.setPrice( request.getParameter( "price" ) ); %>
• D.<jsp:useBean id="product" class="com.example.Product">
  < jsp:setProperty name="product" property="name"
  value="${name}" />
  < jsp:setProperty name="product" property="price"
  value="${price}" />
  < /jsp:useBean>

You have built a web application that you license to small businesses. The webapp uses a context parameter, called licenseExtension, which enables certain advanced features based on your client's license package. When a client pays for a specific service, you provide them with a license extension key that they insert into the <context-param> of the deployment descriptor. Not every client will have this context parameter so you need to create a context listener to set up a default value in the licenseExtension parameter. Which code snippet will accomplish this goal?

• A.String ext = context.getAttribute('licenseExtension');
  if ( ext == null ) {
  context.setAttribute('licenseExtension', DEFAULT);
  }
• B.String ext = context.getParameter('licenseExtension');
  if ( ext == null ) {
  context.setParameter('licenseExtension', DEFAULT);
  }
• C.String ext = context.getInitParameter('licenseExtension');
  if ( ext == null ) {
  context.resetInitParameter('licenseExtension', DEFAULT);
  }
• D.String ext = context.getInitParameter('licenseExtension');
  if ( ext == null ) {
  context.setInitParameter('licenseExtension', DEFAULT);
  }
• E.You cannot do this because context parameters CANNOT be altered programmatically.

Given an HttpServletRequest request and HttpServletResponse response, which sets a cookie "username" with the value "joe" in a servlet?

• A.request.addCookie("username", "joe")
• B.response.addCookie(new Cookie("username", "joe"))
• C.request.addHeader(new Cookie("username", "joe"))
• D.request.addCookie(new Cookie("username", "joe"))
• E.response.addHeader(new Cookie("username", "joe"))
• F.request.setCookie("username", "joe")
• G.response.addCookie("username", "joe")

Given the two security constraints in a deployment descriptor:
1 01. <security-constraint>
1 02. <!--a correct url-pattern and http-method goes here-->
1 03. <auth-constraint><role-name>SALES</role-name></auth-
1 03. <auth-constraint>
1 04. <role-name>SALES</role-name>
1 05. </auth-constraint>
1 06. </security-constraint>
1 07. <security-constraint>
1 08. <!--a correct url-pattern and http-method goes here-->
1 09. <!-- Insert an auth-constraint here -->
1 10. </security-constraint>
If the two security constraints have the same url-pattern and http-method, which two, inserted independently at line 109, will allow users with role names of either SALES or
MARKETING to access this resource? (Choose two.)

• A.<auth-constraint>
  < role-name>MARKETING</role-name>
  < /auth-constraint>
• B.<auth-constraint>
  < role-name>ANY</role-name>
  < /auth-constraint>
• C.<auth-constraint/>
• D.<auth-constraint>
  < role-name>*</role-name>
  < /auth-constraint>