It’s time to put what you’ve learned to the test, get 4 questions right to pass this unit.
Q1.
How do we use the access control roles to restrict access to commerce process or data via OCC customization?
Choose the correct answer.
A
They are specified in the spring-security.xml file against unauthorized REST requests.
B
Roles-related user groups are configured to enable/disable type-based access rights.
C
They are annotated via @Secured to methods in OCC controllers.
D
-spring.xml can be used to relate access control roles to restrict method invocation of spring resources.
Q2.
What should we pay attention to when working with an OCC extension?
There are 2 correct answers.
A
The name of the extension must end with "occ."
B
After implementing a new service, there is no need to register it in -spring.xml as the spring context is automatically filled.
C
We must work in the src folder to implement a web service controller.
D
We must work in the web/src folder to implement a web service controller.
Q3.
What are the major features and benefits of the OCC module?
There are 2 correct answers.
A
It allows Commerce customers to enable touch points and channels without lengthy and costly IT cycles.
B
It enables reusing commerce processes and data.
C
It enables commerce to send data to external systems through RESTful APIs.
D
Its RESTful APIs can be configured in runtime and extended through Backoffice UI.
Q4.
We can use @CacheControl to annotate the controller class for managing caching. Which of the following directive-descriptions are correct when using the annotation?
There are 2 correct answers.
A
PUBLIC - Any cache MAY store the response, unless the response is deemed noncacheable or is only cacheable within a private cache.
B
PRIVATE - The response MUST NOT be used to satisfy a subsequent request without successful validation on the origin server.
C
NO_STORE - A cache MUST NOT store any part of either the immediate request or response.
D
MUST_VALIDATE - Once it has become stale, a cache MUST NOT use the response to satisfy subsequent requests without successful validation on the origin server.
Q5.
What are the typical approaches to define data mappings from a DTO/Model to a WsDTO?
There are 2 correct answers.
A
Declare field mappings in a web context spring XML file.
B
Declare field mappings in the -beans.xml to refer to the WsDTO.
C
Implement a custom Data Mapper and register it in -spring.xml file.
D
Implement a custom Data populator and append it to an existing Data Mapper in