Mulesoft Integration Architect Exam 2023 Questions and
Answers with complete solution
What characterises integration solutions across an enterprise?
- Various systems and applications to connect
- Various stakeholders
- Conflicting goals
- Stakeholders have different assumptions, understandings and language
- Systems have different requirements, reliability, availability and performance
What is the most important objective of an integration solution?
To address the in-scope requirements of stakeholders related to the scenarios and use
cases
Identify stakeholders involved in an integration project?
- Project sponsor: drives the project
- Architects: Responsible for implementation
- System integrators and external stakeholders: responsible for external systems
- Auditors: Verify compliance, policies, integrity
- Users: Enduser of the system
Identify stakeholders related to Anypoint Platform?
- Users
- Administrators
- Developers and Architects
- System integrators and external stakeholders
- Analysts and Managers: responsible for managing the scope, value, costs etc.
What are the main areas which an architect has to deal with?
- Non-technical business vs. technical stakeholders
- End users
- Development vs. deployment vs. runtime operations stakeholders
- Implementers vs. managers. vs. executives
What is Mulesofts point of view on integration solution architectures vs. enterprise
architectures?
1. Integration solutions architecture: Documents individual integration initiatives for
example message-based integration, batch processing, ETL, form of integration
between systems
2. Enterprise architecture: Application network of an organisation. API-Led connectivity,
layering, reusing, combining API-Led
What is Mulesoft's OBD = Outcome based delivery approach?
- 90% of the projects are not reaching their goals
- After few months of production the customer can not use the platform because the
Organisation is not enabled enough
1. Business outcomes = What do we deliver?
,2. Technology delivery = How can we use Anypoint Platform?
3. Org enablement = How can we enable C4E and training?
How are user stories usually documented?
What are the two kinds of requirements which are discovered from user story
perspective?
1. Functional requirements:
- Triggering events
- Acceptance criteria
- Expected errors and error handling
2. Non-functional requirements:
- May be invented by industry or other external authorities
- Are constrains on the requirements
What are typical types of documentation in an integration solution architecture?
- Required use cases
- Views of systems and sub-systems
- Views of data and interfaces
- Functional requirements and non-functional requirements and SLAs
- Views of interactions and design decisions
- Key decisions, requirements and tradeoffs
What is the 4+1 methodology?
- Is one common approach how to illustrate views for software and systems
1. Logical view: Architecture diagram, relationships between systems and stakeholders
2. Process view: API-led diagram, Information about the movement of information,
Documents success and failure paths, Sequence and activity diagrams
3. Development view: Data mapping, testing strategy, Example flows in Mulesoft
4. Physical view: Deployment diagrams, What artefacts are running on each node, how
the different pieces are connected, high level topology: databases, runtimes, workers,
LBs, firewalls, VPCs
+1 = The plus 1 illustrates the scenarios from an end user perspective --> User Stories
,- Design phase: Process view, development view, physical view
What documentation is also required beside 4+1 view?
Maintenance, operations and security documentation
What are Mule applications under the hood?
Java-based applications based on Java Spring configured by Mule application XML files
Which 4+1 view is created to direct deployment and maintenance phases?
Physical view:
- Shows the process and the nodes that are running
- View on CI/CD
What is a Mule application?
- It runs in a Java virtual machine (JVM)
- It is triggered by internal or external events or processes and routes to other
components or endpoints
How does a typical Mule flow looks like?
What are the main elements for a Mule event?
Mule events can be passed or copied between event processors in the flow
- Message: The main data object carried between event processors
- Attributes: Metadata contained in the message header
- Payload: Core information of the message
- Variables: Stores current event state for use by later event processors
- Error message: Generates by the flow
What are the three types of flows in Mule 4?
, 1. Regular
- Starts with a message source
- Can have its own error handler
2. Private flow
- No message source
- Can only be triggered from within the Mule application
3. Sub flows
- No message source like a private flow
- No Error handling (Errors bubble up into the parent flow)
What happens if you route a message with a flow reference to a sub flow?
The flow message is processed synchronously
How can you trigger flows asynchronously from a parent flow?
With the Async scope:
It will copy the message and process it asynchronously in the parent and sub-flow
For example if you want to send e massage to Splunk you can use the async scope
With which component can you trigger flows beside an event source?
Scheduler:
- Fixed frequency: Poll every 1000 mili sec
- Cron: You can specify an event to occur just once at a certain specific date or at some
frequency
When you enable CRON you can see the application on cloud hub an trigger it in the
run time manager
- runtime manager -> schedules
Answers with complete solution
What characterises integration solutions across an enterprise?
- Various systems and applications to connect
- Various stakeholders
- Conflicting goals
- Stakeholders have different assumptions, understandings and language
- Systems have different requirements, reliability, availability and performance
What is the most important objective of an integration solution?
To address the in-scope requirements of stakeholders related to the scenarios and use
cases
Identify stakeholders involved in an integration project?
- Project sponsor: drives the project
- Architects: Responsible for implementation
- System integrators and external stakeholders: responsible for external systems
- Auditors: Verify compliance, policies, integrity
- Users: Enduser of the system
Identify stakeholders related to Anypoint Platform?
- Users
- Administrators
- Developers and Architects
- System integrators and external stakeholders
- Analysts and Managers: responsible for managing the scope, value, costs etc.
What are the main areas which an architect has to deal with?
- Non-technical business vs. technical stakeholders
- End users
- Development vs. deployment vs. runtime operations stakeholders
- Implementers vs. managers. vs. executives
What is Mulesofts point of view on integration solution architectures vs. enterprise
architectures?
1. Integration solutions architecture: Documents individual integration initiatives for
example message-based integration, batch processing, ETL, form of integration
between systems
2. Enterprise architecture: Application network of an organisation. API-Led connectivity,
layering, reusing, combining API-Led
What is Mulesoft's OBD = Outcome based delivery approach?
- 90% of the projects are not reaching their goals
- After few months of production the customer can not use the platform because the
Organisation is not enabled enough
1. Business outcomes = What do we deliver?
,2. Technology delivery = How can we use Anypoint Platform?
3. Org enablement = How can we enable C4E and training?
How are user stories usually documented?
What are the two kinds of requirements which are discovered from user story
perspective?
1. Functional requirements:
- Triggering events
- Acceptance criteria
- Expected errors and error handling
2. Non-functional requirements:
- May be invented by industry or other external authorities
- Are constrains on the requirements
What are typical types of documentation in an integration solution architecture?
- Required use cases
- Views of systems and sub-systems
- Views of data and interfaces
- Functional requirements and non-functional requirements and SLAs
- Views of interactions and design decisions
- Key decisions, requirements and tradeoffs
What is the 4+1 methodology?
- Is one common approach how to illustrate views for software and systems
1. Logical view: Architecture diagram, relationships between systems and stakeholders
2. Process view: API-led diagram, Information about the movement of information,
Documents success and failure paths, Sequence and activity diagrams
3. Development view: Data mapping, testing strategy, Example flows in Mulesoft
4. Physical view: Deployment diagrams, What artefacts are running on each node, how
the different pieces are connected, high level topology: databases, runtimes, workers,
LBs, firewalls, VPCs
+1 = The plus 1 illustrates the scenarios from an end user perspective --> User Stories
,- Design phase: Process view, development view, physical view
What documentation is also required beside 4+1 view?
Maintenance, operations and security documentation
What are Mule applications under the hood?
Java-based applications based on Java Spring configured by Mule application XML files
Which 4+1 view is created to direct deployment and maintenance phases?
Physical view:
- Shows the process and the nodes that are running
- View on CI/CD
What is a Mule application?
- It runs in a Java virtual machine (JVM)
- It is triggered by internal or external events or processes and routes to other
components or endpoints
How does a typical Mule flow looks like?
What are the main elements for a Mule event?
Mule events can be passed or copied between event processors in the flow
- Message: The main data object carried between event processors
- Attributes: Metadata contained in the message header
- Payload: Core information of the message
- Variables: Stores current event state for use by later event processors
- Error message: Generates by the flow
What are the three types of flows in Mule 4?
, 1. Regular
- Starts with a message source
- Can have its own error handler
2. Private flow
- No message source
- Can only be triggered from within the Mule application
3. Sub flows
- No message source like a private flow
- No Error handling (Errors bubble up into the parent flow)
What happens if you route a message with a flow reference to a sub flow?
The flow message is processed synchronously
How can you trigger flows asynchronously from a parent flow?
With the Async scope:
It will copy the message and process it asynchronously in the parent and sub-flow
For example if you want to send e massage to Splunk you can use the async scope
With which component can you trigger flows beside an event source?
Scheduler:
- Fixed frequency: Poll every 1000 mili sec
- Cron: You can specify an event to occur just once at a certain specific date or at some
frequency
When you enable CRON you can see the application on cloud hub an trigger it in the
run time manager
- runtime manager -> schedules
