Passed the Mulesoft Certified Developer(Mule4) Level 1 Exam

This one was a very tough exam to prepare for. Even with having taken the online 5 day Fundamentals course last August. I failed my first attempt of the exam last week. So I booked another schedule the week after and really focused on the skills and concepts I was lacking.

The self study material is now available. Enroll and sign up here https://training.mulesoft.com/course/mulesoftu-fundamentals4

The format of the exam is a multiple choice. There are a total of 60 questions and passing score is 70 and you are alloted 120 minutes.

Start by reviewing the Study Guide

Here are my notes for passing the exam.

  • Creating Application Networks
    • Current IT landscape problem
      • IT cannot delivery fast enough
      • IT can build fast while still early but as time moves the IT project gets complex and harder to build on top of it
      • Solution: A new IT operating model IT builds reusable assets and data Business can self-serve on the assets
    • Modern API  approach
      • discoverable and accessible through self service
      • productized and designed for ease of consumption
      • easily managed for security, scalability and performance
      • API-Led Connectivity
        • Experience API
        • Process API
        • System API
    • What is C4E ?
      • Center for Enablement
      • A cross functional team
        • developers
        • lob it
        • central it
      • C4E make sure assets
        • are productized
        • consumable
        • fully leveraged
      • success is based on asset consumption
    • Deconstructing API
      • What is an API?
        • Acronym for Application Programming Interface
        • it provides information how to communicate with a software component
          • Operations – what to call
          • Inputs – what inputs are expected Output – results expected
          • Underlying data types ?
        • It defines functionalities independent of implementations
          • change what is behind the scenes without people changing how they call it
      • API can be of the following
        • API specification file
          • defines what to call, send and get back
        • web service
          • actual API implementation you can make calls
        • API proxy
          • application that controls access  to a web service, restricting access and usage through an api proxy
      • What are web services
        • different software systems often need to exchange data with each other
          • bridges platform, protocols, programming language and hardware architecture
        • is a method of communication between systems over the internet
        • system interaction manner is prescribed by some defined rules of communication
      • Parts of a web service API
        • The web service api
          • describes how to interact with the api
          • may or may not be defined in a file
        • web service interface implementing an api
          • code providing structure to the application/ combination
        • web service implementation itself
          • actual code and application
      • Two main API types
        • SOAP
          • traditional, more complex
          • communication rules are defined in an XML
        • RESTful
          • recent, simplier
          • uses existing HTTP communication protocol
          • Representational State Transfer
            • architecture pattern where clients and servers exchange representation of resources using HTTP protocols
            • http request methods
              • POST
                • creates new resource
              • GET
                • retrieves current state normally in XML or JSON
              • PUT
                • updates or creates a new one
              • PATCH
                • partially updates
              • DELETE
                • deletes a resource
            • data and resources are represented using URIs
            • resources are accessed or managed with a fixed set of operation
              • get /companies
              • get /companies?country=France
              • etc…
            • Example RESTful web service response
              • JSON (Javascript Object Notation)
                • supports maps and collections
                • lightweight data-interchange format
              • XML
          • Making calls
            • Unsecured API
              • no authentication required
            • Secure API
              • requires credentials or token
              • sometimes api proxies are used to govern access to an api
              • you can secure an api with different protocols OAuth, SAML and JWT
              • Http Status Codes
                • provides feedback for the outcome of the operation
                • good api should return status codes that align with the http spec
  • Designing APIs
    • Modern API
      • productized
      • easily govern
      • build for consumption – reusable
    • Anypoint Design Center
      • Design your api
      • API Designer
        • Uses RAML
    • AnyPoint Exchange
      • A repository
      • library of assets
      • private content only to available to people in your org
      • when a rest api is added to exchange it creates an api portal
      • Flow Designer lightweight version/ available on the web
      • Anypoint Studio for development
      • Anypoint Management Center
        • version proxy
        • rate limit
        • throttling visibility and
        • control scale your application
      • Runtime Services
        • deploy applications
        • lightweight java-based ESB
        • decouples point to point
        • can be deployed anywhere
        • enforces policies for api governance
      • Anypoint Platform
        • uniquely built
        • deploy anywhere
        • can build your own connector
        • have tons of pre-built connectors
        • implemented all the internal process eg. database connection etc..
      • Achieving Success
        • business outcome
        • org enabled technology
        • delivery
        • Paths
          • Plan for success
          • Establish the foundation
          • Build to scale
          • Measure impact
      • API Notebook
        • on exchange you can create documentation – plays your script
      • MUnit
        • test your mule application
    • Mule Applications
      • can be created visually or through xml
      • under the hood it is java using spring
      • mule apps are deployed to mule runtime
    • Mule Runtime Engine
      • lightweight java ESB and integration platform
      • decouples point to point
      • can be deployed anywhere
      • enforces policies for API governance
    • Mule 4 Applications and flows
      • Mule application receive events, process them and route them
      • A listener listens for events
      • an application can consist of single or multiple flows
      • mule event source
        • initiates the execution of flow
      • mule event processors
        • tranform, filter, enrich
    • Workers
      • dedicated instance of mule that runs the app
      • each worker runs in separate containers from every other application
      • can have different compute power
        • apps can be scaled vertically by change worker size
        • apps can be scaled horizontally by adding more workers
      • there are workers in different environments
  • Accessing and Modifying Mule Events
    • Mule event
      • Mule message – data that passes to the flow
      • attribute – metadata in the header payload – core info of the message
      • variables – metadata for the mule event – can be defined and referenced
  • Structuring Mule Applications
  • Building API Implementation Interfaces
  • Routing Events
  • Handling Errors
  • Writing DataWeave Transformations
  • Using Connectors
  • Processing Records
  • Debugging and Troubleshooting Mule Applications
  • Deploying and Managing APIs and Integrations

 

Apologies if this is incomplete but will continue to add the materials on the following days.

Tips and Takeaways From Getting the Apex Specialist Superbadge

I’ve started the new certification path for the Platform Developer II as I already passed the multiple choice question a long time ago but it was ridiculously hard getting a slot on the programming assignment. With this new format, I would need to complete these four superbadges.

So, 1 out 4 completed. I got the Apex Specialist Superbadge nailed.

For the Apex Specialist superbadge. There are a total of 6 mini challenges you need to complete. Requirements are straightforward. If you been developing on the platform for some time, the challenge should be a breeze. It took me 6 hours though to coymplete the challenge.

Takeaways from the challenge

  1. There are many options for building the solution. Just stick with where you are most familiar with.
  2. Use maps for more efficient querying and to bulkify your triggers
  3. I thought I already know all my JSON stuffs until I tried to manually parse a JSON string. Get familiar with using the JSON class methods. Check my post on Demystifiyng JSON parsing in Apex.
  4. Given another chance since the requirements are not that complicated this would’ve been a good practice to have tried test-driven development.

If you need help completing the challenge hit the comments below and I’ll be glad to help. Good luck on getting that superbadge.

Get Creative. Ignore Everbody

Just finished reading this great book by Hugh MacLeod. One of the books recommended by the author of Steal like an Artist. It’s fun and easy to read book. I particularly like the splash of comic strips to each chapter. This book is full of tips to inspire you to get creative, do the stuffs you love doing and not getting bogged down with the money aspects. It is more on finding what makes you tick to be creative and owning that work. Eventually something good would happen.

Check out the blog at https://www.gapingvoid.com/blog/

Get a copy of the book here

2017 Went By and Welcoming 2018

2017 went by so quickly and 2018 already started. Recapping the highlights of 2017 I can say I’ve achieved 3 out of the 5 goals I set earlier this year.

  • I’ve managed to finally revamp the design of this blog and made it mobile friendly, it is not 100% where I want it yet.
  • Started my own channel on Youtube. Just Another Dang How To Channel and gained around 170+ subscribers and 48K views in the first year.
  • Passive income added with some investments in term deposit and bought more Philippine stocks

Then I set out some very ambitious projects that I started but lost steam

  • Registered Quonsepto Limited company
  • Started to create a WP plugin
  • Signed up for Merch by Amazon

For 2018 I won’t put too much attention on the money aspect of doing something. I want to do some damn fine work, something that I enjoy doing and I feel proud of showing it to others.

  • Improve my listing for Merch By Amazon
  • Improve the video quality on my Youtube channel
  • Enhance the usability and creativity of this blog
  • Build my Quonsepto company

For the financial side of things, this is kinda ambitious and far fetch but would like it to be a reality.

  • Pay off the Philippine house loan by the end of 2018
  • Save enough for a downpayment for new house in NZ for 2019.

Just Another Dang How To Channel

Earlier last month I finally started a new Youtube Channel, it was an idea to start a tutorial course for topics I am most passionate about and doing at the moment. I was already doing this by blogging but found that doing video is soo much fun. I have started some PHP HowTos, Salesforce Communities HowTos and some Mac HowTos. I’ll probably match a video tutorial and a blog post in the future. Plan to grow channel with more HowTos as I further develop my skills in Javascript(nodejs, reactjs), mobile development(IOS and Android). Though still in it’s first month I have some decent views and have a very supportive comments from viewers.

Check out my channel and subscribe.

https://www.youtube.com/channel/UCunISgIeaqybaVKJ6Q6n1PA