Choose the code fragment that corresponds to a resource delegating processing of a request to a subresource correctly, when processing the URL "/parent/child" (Choose one):

• A. @Path("/parent")
  class Parent {
  @Path("/child")
  Child getChild() { return new Child(); }
  }
  @Path("/child")
  class Child {
  @GET String getName() { return "name"; }
  }
• B. @Path("/parent")
  class Parent {
  @GET @Path("/child")
  Child getChild() { return new Child(); }
  }
  class Child {
  @GET String getName() { return "name"; }
  }
• C. @Path("/parent")
  class Parent {
  @Path("/child")
  Child getChild() { return new Child(); }
  }
  class Child {
  String getName() { return "name"; }
  }
• D. @Path("/parent") class Parent {
  @Path("/child")
  Child getChild() { return new Child(); }
  }
  class Child {
  @GET String getName() { return "name"; }
  }

If you are developing a Web Service starting from WSDL 1.1, how would you declare in wsdl that the Web Service requires the use of Addressing in a standard and interoperable way.

• A. Declare a policy as
  <wsp:Policy>
  <wsam:Addressing>
  <wsp:Policy/>
  </wsam:Addressing>
  </wsp:Policy>
  and attach it the corresponding wsdl:service so that it applies to all the wsdl:ports in the service
  scope.
• B. Declare a policy as
  <wsp:Policy>
  <wsam:Addressing>
  <wsp:Policy/>
  </wsam:Addressing>
  </wsp:Policy>
  and attach it the corresponding wsdl:binding so that it applies to all the wsdl:operations in its
  scope.
• C. Declare a policy as
  <wsp:Policy>
  <wsam:Addressing wsp:Optional="true">
  <wsp:Policy/>
  </wsam:Addressing>
  </wsp:Policy>
  and attach it the corresponding wsdl:portType so that it applies to all the wsdl:operations in its
  scope.
• D. Declare a policy as
  <wsp:Policy>
  <wsam:Addressing wsp:Optional="true">
  <wsp:Policy/>
  </wsam:Addressing>
  </wsp:Policy>
  and attach it the corresponding wsdl:binding so that it applies to all the wsdl:operations in its
  scope.

Given the JAX-RS root resource class fragment: Choose the statement that best describes the configuration that would be required to support the access control constraint shown:

• A. The developer will have to turn on authentication in the web container configuration file, so that all incoming requests are authenticated in order to be processed.
• B. The developer will have to configure the web container to require authenticated access to the URLs corresponding to this resource, so the proper information can be propagated to the EJB container.
• C. The developer will have to configure the web container to require authenticated access to the URLs corresponding to this resource, and then map web-tier roles to ejb-tier roles, since the JAXRS and EJB runtimes cannot use the same set of roles.
• D. No further configuration is required - the JavaEE runtime will pick up the security constraint and configure the web container to match.

Given the resource class fragment: Choose the code fragment below that would secure access only to the Resource update() method (Choose one):

• A. <security-constraint> <web-resource-collection> <url-pattern>/rest</url-pattern> <http-method>POST</http-method> </web-resource-collection>
• B. <security-constraint> <web-resource-collection> <url-pattern>/rest</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> </web-resource-collection>
• C. <security-constraint> <web-resource-collection> <url-pattern>/rest/id</url-pattern> <http-method>POST</http-method> <http-method>GET</http-method> </web-resource-collection>
• D. <security-constraint><security-constraint> <web-resource-collection> <url-pattern>/id</url-pattern> <http-method>POST</http-method> </web-resource-collection>