|Exam Name||:||IBM WebSphere DataPower SOA Appliances Firmware V3.6.0|
|Questions and Answers||:||74 Q & A|
|Updated On||:||January 19, 2018|
|PDF Download Mirror||:||000-284 Brain Dump|
|Get Full Version||:||Killexams 000-284 Full Version|
must make every effort to complete each transaction but are required to impose a limit of 600 transactions every minute. What can they do to implement this restriction while making efforts to complete each transaction request?
Specify a Request Web Service Proxy SLM action for each Operation specified in the WSDL. Use an Interval of 60, a Rate of 600, and an Action of Shape.
Specify a Request Web Service Proxy SLM action at the Proxy level. Use an Interval of 60, a Rate of 600, and an Action of Throttle.
Specify a Request Web Service Proxy SLM action at the WSDL level. Use an Interval of 60, a Rate of 600, and an Action of Throttle.
Specify a Request Web Service Proxy SLM action at the WSDL level. Use an Interval of 1, a Rate of 600, and an Action of Shape.
Specify a Request Web Service Proxy SLM action at the WSDL level. Use an Interval of 60, a Rate of 600, and an Action of Shape.
What is the difference between a Web Service Proxy Request SLM action of Shape and an action of Throttle?
The Throttle action will discard transactions above the specified rate; Shape will attempt to queue transactions above the specified rate for later transmission.
The Shape action will discard transactions above the specified rate; Throttle will attempt to queue transactions above the specified rate for later transmission.
The Throttle action will discard transactions above the specified rate; Shape uses the Log Target specified to generate an SNMP alert.
The Shape action will discard transactions above the specified rate; Throttle uses the Log Target specified to generate an SNMP alert.
The Shape action will discard transactions above the specified rate; Throttle uses the Log Target specified to generate a log message.
Which monitor definition is needed if a Service Level Agreement states that if the average
response time for a transaction, as measured from entry into the appliance to response back to the client, exceeds 0.2 seconds, then subsequent traffic is to be refused?
Define a Message Filter Action "MFR" with type of "reject". Define a Message Duration Monitor that has a "Measure" of type "messages", and a Threshold/Filter of "Value" set to "200" and an "Action" of "MFR".
Define a Message Filter Action "MFS" with type of "shape". Define a Message Duration Monitor that has a "Measure" of type "messages", and a Threshold/Filter of "Value" set to "200" and an "Action" of "MFS".
Define a Message Filter Action "MFR" with type of "reject". Define a Message Count Monitor
that has a "Measure" of type "requests", and a Threshold/Filter of "Interval" set to "1000", "Value" set to "200" and an "Action" of "MFR".
Define a Message Filter Action "MFS" with type of "shape". Define a Message Count Monitor that has a "Measure" of type "requests", and a Threshold/Filter of "Interval" set to "1000", "Value"
set to "200" and an "Action" of "MFS".
Which DataPower configuration object is NOT a component of an SLM Statement?
A DataPower service is configured to communicate with a backend application server via HTTP
on TCP Port 80. The device's System Logs indicate that the service cannot connect to the backend application server (Unable to establish backside connection). How should it be verified whether the DataPower device has connectivity to the backend server on the TCP port in question?
Enable MultiStep Probe on the service in question and look for connectivity details in the Probe Trace
Use TCP Connection Test from the Troubleshooting control panel
Enable XML File Capture and view connectivity information in the response capture path
Use Generate Error Report and reference TCP/IP error details in the Connectivity section of the report
A company has been testing an XML Firewall using the MultiStep Probe. What will the Export
Capture feature of the Probe provide?
An export of Input data to the Firewall.
An export of the XML Firewall configuration.
An export of the XML Firewall configuration and an export of all transactions currently
available in the probe. Input data to the Firewall will be, in most cases, extracted and stored in the local: directory.
An export of the XML Firewall configuration and an export of all transactions currently available in the probe. Input data to the Firewall will be, in most cases, extracted and stored in the
An export of the XML Firewall configuration and an export of all transactions currently
available in the probe. Input data to the Firewall may be, in most cases, extracted from the INPUT context of the request transactions.
Refer to the Exhibit. A consultant is engaged with an existing customer for a project that requires the deployment of 4 new XS40s to an existing pool of 5 XI50s. The customer is using basic security functionality, so the sales team offered the XS40s to close the deal. In order to keep all the devices in sync with the implementation, the customer provides a domain configuration export from one of the existing XI50s. After importing the domain to one of the new XS40s, the error log shows the information in the exhibit. Why did this happen?
Configurations from XI50s are never portable to the XS40s.
The error report was a legacy from the original device and can be ignored.
The configuration provided for the XS40 is using exclusive XI50 features.
XS40s and XI50s can’t be mixed on the same pool of appliances.
Refer to the Exhibit. After configuring an XML Firewall with inbound SOAP traffic and XML
outbound traffic, the system log shows the information in the exhibit. What does the log analysis show?
The inbound traffic is valid XML but invalid SOAP.
The outbound traffic is valid XML but invalid SOAP.
The outbound traffic is invalid XML and invalid SOAP.
The inbound traffic is invalid XML and invalid SOAP.
Which three statements are true about the product's network Packet Capture troubleshooting
Packet Capture files are stored on the device's 'temporary:' directory.
Packet Captures must be started from the 'default' Application Domain.
Packet Capture works by placing the specified Ethernet interface in Promiscuous Mode,
thereby capturing all traffic appearing on the Ethernet segment to which the interface is attached.
A Packet Capture runs until the 'Maximum Duration' time has expired and keeps the last
"Maximum Size" kilobytes of capture data.
The device's Packet Capture files are in 'pcap' format and are readable by any 'pcap' compliant
application, such as 'tcpdump' or 'ethereal/wireshark'.
Clicking the "Stop Packet Capture" button causes the packet capture to terminate immediately
and the capture data is discarded.
The MultiStep Probe allows for the display of local and global variables. Given the following
--- request 'setVariables_Rule_0' [up] matching matchAll --- setvar INPUT var://local/variable A fetch local:///fee.soap feeSOAP
setvar INPUT var://context/myContext/variable B
xform INPUT local:///getRequestResponseVariables.xsl tempvar4
xform feeSOAP local:///getRequestResponseVariables.xsl OUTPUT
--- response 'setVariables_Rule_1' [up] matching matchAll --- xform INPUT
Which statement is true regarding the two setvar commands?
var://local/variable is a local variable that is only available in the INPUT context of the request side rule. var://context/myContext/variable is a named context variable that is accessible
from any context in the request or response side rules.
var://local/variable is a local variable that is only available in the INPUT context of the request side rule. var://context/myContext/variable is a named context variable that is accessible from any context and in any transaction subsequently processed by the device.
var://local/variable is a local variable that is only available in the INPUT context in the request
or response side rules. var://context/myContext/variable is a named context variable that is accessible from any context in any transaction subsequently processed by the device.
var://local/variable is a local variable that is only available in the INPUT context in the request side rule. var://context/myContext/variable is a named context variable that is accessible
from any context in any transaction subsequently processed by the device via a Service defined within the current domain.
var://local/variable is a local variable that is only available in the INPUT context in the request side rule. var://context/myContext/variable is a named context var.
Cyber Monday Sale! 40% Off
Get Unlimited Access to all ExamCollection's PREMIUM files!
Enter Your Email Address to Receive Your 40% Off Discount Code
Please enter a correct email to Get your Discount Code
Download Free Demo of VCEExam Simulator
Experience Avanset VCE Exam Simulator for yourself.
Simply submit your e-mail address below to get started with our interactive software demo of your free trial.
Start display at page:
Download "CERTIFIED MULESOFT DEVELOPER EXAM. Preparation Guide"
1 CERTIFIED MULESOFT DEVELOPER EXAM Preparation Guide v. November, 2014
3 TABLE OF CONTENTS Table of Contents... 3 Preparation Guide Overview... 5 Guide Purpose... 5 General Preparation Recommendations... 5 Required Experience... 5 For Further Information... 5 Exam Overview... 6 To Register for the Exam... 6 Exam Objective... 6 Intended Audiences... 6 PassFail Requirement... 6 Cost... 7 Exam Format... 7 Testing Location... 7 Certification Validity... 7 Exam Module Details... 8 Basics... 8 Batch... 8 Cache Scope... 8 Clusters... 8 Common Error Scenarios... 9 DataMapper... 9 Deployment and Management Consoles
4 Enricher... 9 Exceptions Expression Routing Expressions Flows and Testing General Knowledge Questions HTTP Java Custom Components Database JMS MuleSoft Solutions Place in the Enterprise Properties REST Routing SOAP Web Services Transactions VM Transport Sample Exam Questions Solutions to Sample Questions
5 PRERATION GUIDE OVERVIEW GUIDE PURPOSE The purpose of this guide is to help those looking to become a Certified MuleSoft Developer understand what knowledge and skills are recommended to pass the exam. This guide does not provide that knowledge. It simply details what knowledge is required and how to obtain that knowledge. Further details can be found on our certification website at and our certification frequently asked questions page at GENERAL PRERATION RECOMMENDATIONS It is suggested, but not mandatory, that an individual first achieve Associate MuleSoft Developer accreditation prior to attempting Certified MuleSoft Developer exam. Relevant additional details can be found at: To prepare for taking the Certified MuleSoft Developer exam, a participant should be able to fully comprehend the concepts described under the Exam Module Details section below and apply the concepts in order to answer exam questions on topics related to each module. For the latest MuleSoft product documentation, please You may also find that some of our courses are helpful in preparing for the Certified MuleSoft Developer exam, such as our Anypoint Platform Essentials and Advanced Anypoint Platform Development courses, but really no course could provide the real project experience needed to pass this challenging exam. REQUIRED EXPERIENCE This test is designed to verify product expertise gained through significant experience using MuleSoft products on a variety of projects. There is no specific amount of experience required, but history shows that people who pass this challenging exam have months or years of real MuleSoft project experience. The exam aims to ensure that each individual has: strong applicable software development background; broad and deep knowledge of MuleSoft solutions and tools; and appreciable experience using MuleSoft solutions on multiple types of real or experimental projects. FOR FURTHER INFORMATION For questions related to MuleSoft CERTIFICATION that are not addressed in this document, please Our certification frequently asked questions site at 5
6 the MuleSoft Certification team at For questions related to MuleSoft TRAINING that are not addressed in this document, please Our Training website at Our training frequently asked questions site at the MuleSoft Training team at EXAM OVERVIEW TO REGISTER FOR THE EXAM To view delivery options and testing center locations, and to purchase and schedule exams, please visit the MuleSoft Webassessor site at:
7 COST The fee is $250 USD per person per attempt to take the Certified MuleSoft Developer exam. Please note that this exam may in some cases be purchased in a bundle or package with other training andor certification exams (see EXAM FORMAT Number of QuestionsFormat: 100 multiple- choice questions Duration: Up to 2 hours Language: English Resources Allowed: None. This is a Closed Book exam. Proctoring: Required. A testing proctor will supervise you taking the exam, either in a testing center on online (see more details below). TESTING LOCATION This examination is available anywhere worldwide. You have two delivery options: In any testing center location within Kryterion s network worldwide; Online from any Internet- connected PC worldwide with qualifying webcam and utilizing Kryterion Webassessor s Online Proctoring service. CERTIFICATION VALIDITY The Certified MuleSoft Developer accreditation has an expiration of two (2) years from the date of passing. 7
8 EXAM MODULE DETAILS The following sections provide key concepts and detailed information on the modules covered in the Certified MuleSoft Developer exam. To prepare for taking the exam, a participant should be able to fully comprehend the concepts described under each module below and apply the concepts in order to answer exam questions on topics related to each module. For the latest MuleSoft product documentation, please Basics This Basics module provides focuses on providing the understanding of the Mule Flow concept with Mule messages, major components, and basic configuration of HTTP, Java Component, etc. Steps to creating a Project in Mule How a Flow applies to a Mule Message Source and a Message Processor Major components of a Mule Message Procedural coding approach with Mule development Basic Mule configuration of transport protocols, endpoints, and POJO manipulation Batch The batch module reviews the new batching feature implemented in 3.5. The various phases of batch processing Configuring batch processing Cache Scope The Cache Scope module reviews how the Cache Scope strategy supports time saving and processing load by storing and reusing frequently called data. How to add and configure a Cache Scope Creating a new Caching Strategy and best practices for managing through application code Clusters The Clusters module provides an overview of the how to manage server clusters and the relations with Mule Enterprise Service Bus (ESB) implementation. 8
9 Understanding general concepts and benefits for building Mule Clusters How Mule Clusters use queues to distribute application flows for processing A review of how clustering supports various Mule transport mechanisms Common Error Scenarios The Common Error Scenarios module details common error situations during MuleSoft development and related exception strategies used for dealing with issues. Global application configuration for handing exceptions Anypoint Studio error scenario navigation Working with debugging Flows and expression handlers DataMapper The DataMapper module reviews how mapping flows can define overall data transformation and integration process from a given input to a given output. How to use the Anypoint DataMapper component and common implementation scenarios Working with the JSON data type and how it applies to a DataMapper Using the Object to String transformer Data model code translation and usage with a Mule message Deployment and Management Consoles The Deployment and Management Consoles module provides an overview of configuring an application environment, managing user community, and deployment procedures using MMC. Using the general step- by- step process for deploying an application to a server using the Mule Enterprise Management and CloudHub consoles Configuring Mule ESB and CloudHub for application deployment Organizing spring properties and spring property file configuration How to use Flow Analyzer to review aspects of Flows in a application and why this is critical during configuration and application deployment Enricher The Enricher module covers how Enrichers can be used to enhance a Mule message. 9
10 How the Message Enricher processes data and relevant use cases Understanding complex enrichment Exceptions The Exceptions module evaluates the available Exception strategies, usage of the Exception strategies, and how they affect Flows and Sub- Flows. Using Exception Strategies and how they affect FlowsSub- Flows The different exception strategies that are available How to change and return a message from an Exception strategy Routers that are for potential error conditions (First Successful, Until Successful) Expression Routing The Expression Routing module provides a review of routing techniques using Expressions. See the Expressions description and, to a lesser degree, the Routing description. See Expressions and, to a lesser degree, Routing. Expressions The Expressions module provides a review of all expressions properties, and inboundoutbound routing ways of using expressions. Inbound- outbound Expression properties Using Flow variables and session variables for expression evaluation How Maps and Lists are evaluated andor manipulated using Expressions Setting variable and property elements using Expressions Setting and testing Payload attributes through Expressions using components such as Expression Transformers, Filters, Choice Router, and Loggers Flows and Testing The Flows and Testing module conducts focuses on how to develop various flow types and how to unit test all message Flow techniques. How to unit test various endpoints 10
11 Coding and testing exchange patterns (e.g., request- response and one- way) Understanding the differences between inbound and outbound endpoints Testing using JUnit cases with MuleSoft Procedures for sending a Mule message from test class to a MuleSoft application General Knowledge Questions The General Knowledge Questions module covers basic MuleSoft implementation and design concepts. Creating Flows and how to use message processors Steps when debugging Flows and common error scenarios Understanding data movement through an application and is encapsulated with Mule Logic HTTP The HTTP module focuses on the concept for building HTTP connector flows, logging, and processing in Anypoint Studio. Understanding how to create and configure an HTTP endpoint, inbound and outbound What the differences are between HTTP and HTTPS Building independent HTTP flows in Anypoint Studio Understanding HTTP content- type and the effect on browser types Java Custom Components The Java Custom Components module reviews creating and testing Java custom components and integrating them into flows. Using advanced Java concepts to invoke service calls for passing Mule messages Creating Mule transformers using custom- made Java classes Configuring Java components such as prototype and singleton Usage of the default entry point resolver with Java components Database The Database module focuses on database connectors and data source customization for endpoints within flows. Understanding contents of database connectors and associated data sources 11
12 How database operations differ and their limitations Database return types and how to access the contents of the returned objects using Expressions Using SQL for DataMappers and Expressions JMS The JMS module provides an overview of building JMS connectors including attributes such as creating two- way communications, temporary queues, and serializing objects to send over transports. Understanding general usage and configuration concepts of using JMS Using back channels and creating two- way communication through JMS connections How JMS queues differ from Topics Understanding how JMS uses Correlation IDs, serializing, and deserializing objects MuleSoft Solutions Place in the Enterprise This module outlines how systems, data, and applications can be integrated within an enterprise and discusses the potential business impact. Understanding integration points for Mule ESB within an enterprise Benefits of using Mule ESB Properties This module reviews Mule properties, properties file configuration, and other configurable parameters. Reviewing how to develop and manage application properties Benefits for using global properties REST The REST module provides an overview of REST basics, method usage, dynamic endpoints, and absorbing resources. Understanding the basics of implementing a REST services and the methods used such as GET, POST, PUT, and DELETE Review how to use annotations on REST methods to create unique signatures Usage of REST blocks and how to absorb resources Understanding how to create REST clients and working with dynamic endpoints 12
13 Routing The Routing module reviews the different types of Routers and how Routers are used to control how messages are sent and received by components. Defining and basic creation and control of Mule Flows, Sub- Flows, and Flow- Reference Understanding Filters and how to other basic filters are used with Routing Usage techniques for Splitters, Aggregators, Multi- Cast Routers, and For- each SOAP Web Services The SOAP Web Services module provides an overview of using SOAP web service concepts for publishing andor consuming a Mule message. Learning and applying the basics of a SOAP message with Mule Understanding how to use CXF Interfaces to create Service definitions Extending interfaces to create CXF implementations Sending and receiving Mule messages over HTTP Transactions The Transactions module reviews how to apply the concept of transaction management and which endpoints support this transaction. Managing and configuring resource transactions for inbound and outbound messages Understanding the various transaction types and usage techniques VM Transport The VM Transport module reviews how to use a VM Transport for controlling how messages are sent and received by components in the system. How to use VM Transport for communication between Mule flows Queue usage with VM Transport and configuration structure 13
14 SAMPLE EXAM QUESTIONS Solutions to these questions are provided in the next section. Question 1. Can a flow have more than one message source? A. Yes, using the composite source B. Yes, if declared sequentially at the beginning of the flow C. No, Mule validates on startup that the next element after a message source is a message processor D. It depends on if the two message sources have compatible transport types. Question 2. Which of the following transformations is not possible when using DataMapper? A. Excel Spread 000-284 Sheet to a CSV file B. CSV file to a POJO C. XML file to Map D. JSON to HTML Question 3. Fill in the Blank: Mule ESB and CloudHub can have multiple, each of which can be transmitting concurrent. A. Applications, Messages B. Nodes, Loads C. Flows, Endpoints D. Endpoints, Workers Question 4. Where can't I define an Exception Strategy? A. Sub- flow B. Flow C. Private flow D. Global configuration Question 5. Expressions can be used in MuleSoft integration: A. To extract information from the current message B. With routers and filters for defining routing logic C. For filtering out unwanted messages 14
15 D. All of the above Question 6. In order to Unit test a MuleSoft application it's necessary to extend what class? A. org.mule.tck.junit4.functionaltestcase B. org.mule.tck.functional.functionaltestcomponent C. org.mule.tck.exceptions.functionaltestexception D. org.junit.test Question 7. One can use Mule Expression Language in which of the following contexts? A. Application B. Message C. Server D. All Question 8. When receiving HTTP responses, the payload of the MuleMessage will always be: A. A hashmap of all query parameters B. An InputStream C. Dependent on the URL and how it comes to Mule (webserver, proxy, etc.) D. Either JSON, a string or a hashmap depending on the request Question 9. If the component implements Callable lifecycle interface, what method would you use to receive the message? A. oncall() B. initialize() C. Start() D. None of the above Question 10. What are the databases that MuleSoft integrations can connect to? A. Any JDBC compliant database B. Oracle, MySQL, Postgres, Derby, DB2, MSSQL C. Any database D. Oracle and Postgres 15
16 Question 11. What is the purpose of setting the maxredelivery attribute on the connector URL? A. To deliver each message in the queue up to the value set in maxredelivery, without differentiating between messages that generated errors and others B. That attribute is not possible to set on a JMS connector C. To avoid an infinite loop trying to process a message that will always generate an error D. To define the maximum number of receivers for the message Question 12. What's the correct way to define a dynamic inbound endpoint? A. Dynamic endpoints are only supported for outbound endpoints B. <inbound- endpoint host=" " path="#[expresion.for.path]" port="port" > C. <inbound- endpoint address="
17 SOLUTIONS TO SAMPLE QUESTIONS Question Correct Answer 1 A 2 D 3 A 4 A 5 D 6 A 7 D 8 B 9 A 10 A 11 C 12 A 13 C 14 B 17
AquaLogic Service Bus
AquaLogic Bus Wolfgang Weigend Principal Systems Engineer BEA Systems 1 What to consider when looking at ESB? Number of planned business access points Reuse across organization Reduced cost of ownership
More information Apigee Gateway Specifications
Apigee Gateway Specifications Logging and Auditing Data Selection Requestresponse messages HTTP headers Simple Object Access Protocol (SOAP) headers Custom fragment selection via XPath Data Handling Encryption
More information Network Agent Quick Start
Network Agent Quick Start Topic 50500 Network Agent Quick Start Updated 17-Sep-2013 Applies To: Web Filter, Web Security, Web Security Gateway, and Web Security Gateway Anywhere, v7.7 and 7.8 Websense
More information WorkflowBusiness Process Management
1 WorkflowBusiness Process Management Andy C. Tran Staff Systems Engineer 2 Agenda Business Process Management Overview Demo 3 Generic Case based Work Flow Pattern Case Initiation Case Assessment & Assignment
More information Enterprise Service Bus
We tested: Talend ESB 5.2.1 Enterprise Service Bus Dr. Götz Güttich Talend Enterprise Service Bus 5.2.1 is an open source, modular solution that allows enterprises to integrate existing or new applications
More information Software Architecture Document
Software Architecture Document Project Management Cell 1.0 1 of 16 Abstract: This is a software architecture document for Project Management(PM ) cell. It identifies and explains important architectural
More information Pre-Installation Instructions
Agile Product Lifecycle Management PLM Mobile Release Notes Release 2.0 E49504-02 October 2014 These Release Notes provide technical information about Oracle Product Lifecycle Management (PLM) Mobile 2.0.
More information Check list for web developers
Check list for web developers Requirement Yes No Remarks 1. Input Validation 1.1) Have you done input validation for all the user inputs using white listing andor sanitization? 1.2) Does the input validation
More information Java SE 8 Programming
Oracle University Us: 1.800.529.0165 Java SE 8 Programming Duration: 5 Days What you will learn This Java SE 8 Programming training covers the core language features and Application Programming
More information Setting Up an AS4 System
INT0697_150625 Setting up an AS4 system V1r0 1 Setting Up an AS4 System 2 Version 1r0 ENTSOG AISBL; Av. de Cortenbergh 100, 1000-Brussels; Tel: +32 2 894 5100; Fax: +32 2 894 5101; infoentsog.eu, .entsog.eu,
More information WebSphere ESB Best Practices
WebSphere ESB Best Practices WebSphere User Group, Edinburgh 17 th September 2008 Andrew Ferrier, IBM Software Services for WebSphere andrew.ferrieruk.ibmm Contributions from: Russell Butek (butekus.ibmm)
More information Getting started with API testing
Technical white paper Getting started with API testing Test all layers of your composite applications, not just the GUI Table of contents Executive summary... 3 Introduction... 3 Who should read 000-284 this document?...
More information WEBLOGIC ADMINISTRATION
WEBLOGIC ADMINISTRATION Session 1: Introduction Oracle Weblogic Server Components Java SDK and Java Enterprise Edition Application Servers & Web Servers Documentation Session 2: Installation System Configuration