MCD - Level 1 / Development Fundamentals (Mule 4) Quiz & DIY Exercises
Introducing Application Networks and API-Led Connectivity
Q.1:
What MuleSoft API-led connectivity layer is intended to expose part of a backend database without business logic?
- Experience
- Data
- System
- Process
- Security
Q.2:
What statement is part of MuleSoft's description of an application network?
- Creates reusable APIs and assets designed to be consumed by other business units
- Creates and manages high availability and fault tolerant services and infrastructure
- Leverages Central IT to deliver complete point-to-point solutions with master data management
- Creates and manages a collection of JMS messaging services and infrastructure
Q.3:
According to MuleSoft, what is the Center for Enablement's role in the new IT operating model?
- Creates and manages discoverable assets to be consumed by line of business developers
- Centrally manages partners and consultants to implement line of business projects
- Implements line of business projects to enforce common security requirements
- Produces and manages API policies for line of business deployments
Q.4:
What is a core characteristic of the Modern API?
- API is designed first using an API specification for rapid feedback
- API is rapidly prototyped following AGILE methodology
- API follows the RESTful architecture
- API has a mechanism to accept feedback and suggestions for improvement
Q.5:
What HTTP method in a RESTful web service is typically used to completely replace an existing resource?
Q.6:
Refer to the exhibit. The API specification supports searching for articles on the searchworld.org site.
What is the most idiomatic (used for its intended purpose) URL and method to retrieve articles about "einstein" in XML format?
Q.7:
MuleSoft API-led connectivity layer APIs are developed to play a specific role.
What are the roles of the System -> Process -> Experience APIs?
- Unlocking data from systems -> delivering an experience -> composing data into processes
- Unlocking data from systems -> composing data into processes -> delivering an experience
- Delivering an experience -> unlocking data from systems -> composing data into processes
- Delivering an experience -> composing data into processes -> unlocking data from systems
Q.8:
API-led connectivity not only depends on three categories of reusable APIs to compose new services and capabilities, but also decentralizes and democratizes access to enterprise data.
What is the Not Correct in the given context?
- Central IT produces reusable assets, and in the process unlocks key systems, including legacy applications, data sources, and SaaS apps
- Central IT and other teams can then reuse these API assets and compose process level information.
- Then, app developers can discover and self-serve on all of these reusable assets, creating the experience layer of APIs and ultimately the end-applications
- This API-led approach to integration slows speed, and productivity
- This API-led approach to integration increases agility, speed, and productivity
Q.9:
Why is API-led connectivity necessary?
- API-led connectivity is an important integration strategy because the technologies that enterprises are using to engage with their customers, employees, and partners have changed dramatically.
- The convergence of enterprise technologies like IoT, SaaS, big data, social, mobile, and APIs are providing powerful new tools to allow businesses to do more, unlock new revenue streams, understand their customers better, and innovate faster than ever before. But to do so, they need to integrate these new technologies with APIs.
- Traditionally, these integrations have been done via point-to-point connections, done in an ad hoc way whenever a project requires. This leads to complicated and brittle systems that are prone to failure and require a great deal of IT’s time and resources to maintain
- The speed of these changes cannot be accommodated by traditional point-to-point integration methods. Another approach is required — API-led connectivity.
- All are correct
Q.10:
What is IT delivery gap?
- IT is often tasked with implementing new technologies, and making the necessary changes, as well as maintaining legacy systems (and their connections to other systems).
- The requests IT must fulfill is ever-growing, even as their resources stay constant.
- The number of new projects necessary to implement today’s technology needs are measured against IT’s capacity to deliver them and, is spiraling ever upward
- As the technology requirements of the business continue to grow in a multiplicative fashion, IT’s resources only grow in a linear way, no matter how many resources a business can throw at the problem
- All are correct.
Q.11:
API-led connectivity provides?
- An approach for connecting and exposing assets by connecting things point-to-point
- An approach for connecting and exposing assets. Every asset becomes a managed API – a modern API, which makes it discoverable through self-service without losing control
- System APIs used in an API-led approach to connectivity provides system user experience
- Process APIs used in an API-led approach to connectivity provides a way to connect to core assets
Q.12:
What is the correct statement about the APIs used in an API-led approach to connectivity?
- Process APIs – These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered
- System APIs – these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects
- Experience APIs – Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind
- All are correct.
Q.13:
What are the business benefits of API-led connectivity?
- It enables you to move fast on your first project, but then actually accelerate further from your second project onwards, due to reusable assets and a built-up organizational capability; API-led connectivity liberates resources, allowing you to innovate and to move quickly.
- To delivering IT projects ensures you are not only on time and budget with your first projects, but you have built the reusable assets that will save your company time and money, created an infrastructure which is designed for change, built in visibility, compliance and governance and, most importantly, met the needs of the business, which is long-term sustained agility.
- Increases in agility and speed provided by API-led connectivity led to delivering projects 3-5x faster and increased team productivity by 300%, compared to legacy or homegrown integration solutions.
- All are correct.
Q.14:
IT sectors today in which IT delivery gap has already started to grow and only going to grow in future?
- Digital Competition
- Mobile
- Big Data, Analytics
- Cloud and SaaS
- All of the above
Q.15:
MuleSoft is a new way of working to close the delivery gap, the New IT operating model is based on?
- For any new demand of IT, more assets can be added or deployed to close the delivery gap
- This new model is time consuming and only going to cost more to business
- Enablement and assets of IT are constant with time and consumption and innovation is increased to meet the demands on IT.
- None of the above is correct.
Q.16:
The new operating model emphasizes consumption in which?
- Reusable assets are produced, those are self-service and discoverable
- Reusable assets are consumed by LoB IT and developers and provide Feedback and Usage metrics.
- Center IT unlocks the assets and LoB IT or Central IT produces reusable assets.
- All are correct
Q.17:
A common project-based approach considers the project to be delivered on time and within budget with a great success. But problem is?
- Limited opportunity for reuse
- Tight coupling = brittleness
- Difficult to govern
- Sometime meets partial business requirements
- All of the above
Q.18:
Which is not the core characteristic of Modern API?
- Discoverable and accessible through self-service
- Productized and designed for ease of consumption
- Time consuming and sometimes out of the business budget
- Easily managed for security, scalability, and performance
- All are correct
Q.19:
Unlocking the assets and decentralize access through System APIs is done by?
- Developers
- LoB IT
- Central IT
- UX designers
- Application Architects
Q.20:
LOB IT team is responsible for?
- Discover, self-serve, reuse and Consume the assets and build the experience APIs
- Discover, reuse assets and Compose information through Process APIs
- Unlock assets and decentralize access through System APIs
- Unlock, Compose and Consume the assets through APIs
- None of these
Q.21:
What is not the drive outcomes with API-led connectivity?
- Designs in readiness for change
- Time consuming and out of budget sometime
- Drives reuse vs build
- Builds in governance, compliance, security, and scalability
- Meets the needs of the business
Q.22:
What is not true about Center for enablement(C4E)?
- Success of C4E measured on asset consumption
- C4E is a cross functional team
- C4E ensures that assets are Productized and published
- C4E ensures that assets are Consumable, Consumed broadly
- C4E blocks the full leveraged of assets
Q.23:
What is not correct about an application network?
- Is recomposable: it bends, not breaks – built for change
- Provides visibility, security and governability at every API node
- Based on Speed, Agility and Innovation
- Every project does not add value to the application network
- Emerges bottoms-up via self-service
Q.24:
What exactly is an API or Application Programming Interface? Identify which is not true.
- It provides the info for how to communicate with a software component
- It defines the Operations (what to call), Inputs (what to send with a call), Outputs (what you get back from a call),Underlying data types
- It provides the necessary implementations to configure the API
- It defines functionalities independent of implementations
- All are correct
Q.25:
What do people mean when they say API?
- A web service
– The actual API implementation you can make calls to or the interface of that API
implementation
- An API proxy
– An application that controls access to a web service, restricting access and usage
through the use of an API gateway
- An API interface definition file (API specification)
– Defines what you can call, what you send it, and what you get back
- All are correct
Q.26:
What is a web service?
- A web service is a method of communication that allows two software systems to exchange data over the internet
- Systems interact with the web service in a manner prescribed by some defined rules of communication
– How one system can request data from another system, what parameters are required, the structure of the return data, and more
- The web service API describes how you interact with the web service
- The web service interface implementing the API is the code providing the structure to the application so it implements the API
- The web service implementation itself is the actual code and application
- All of the above
Q.27:
What is not true about web services?
- SOAP and RESTful are two main types of web services
- The communication rules are defined in an XML-based WSDL (Web Services
Description Language) file for SOAP web services
- RESTful web services use the existing HTTP communication protocol
- RESTful web services recent, very complex type
- SOAP web services are traditional, more complex type
Q.28:
In RESTful web services, what operation should be performed on the object identified by the URL, based on?
- HTTP protocol
- HTTP Request method
- HTTP Request Headers
- HTTP Request Query Parameters
- HTTP Request Body
Q.29:
RESTful web service request methods operations are listed.
1. Replaces a resource completely – If the resource doesn't exist, a new one is created
2. Deletes a resource
3. Creates a new resource
4. Partially updates a resource with submitted data
5. Retrieves the current state of a resource in some representation (usually JSON or XML)
What is the correct order of request methods?
- POST, GET, PUT, DELETE, PATCH
- PUT, DELETE, PATCH, POST, GET
- PUT, DELETE, POST, PATCH, GET
- GET, PUT, POST, DELETE, PATCH
Q.30:
In Making calls to RESTful Secured APIs, what is not true?
- The API may be public and require no authentication
- The API may be secured and require authentication
- You may need to provide credentials and/or a token
- Often a proxy is created to govern access to an API
- We will call and then later create an API secured by credentials
- We can also secure an API with other authentication protocols OAuth, SAML, JWT, and more
Q.31:
Common HTTP status codes and their definition are given, what is not correct about them?
- Code 200 means OK – The request succeeded is returned by GET, DELETE, PATCH, PUT
- Code 201 means Created – A new resource or object in a collection and returned by POST
- Code 304 means Not modified – Nothing was modified by the request of PATCH, PUT
- Code 400 means Bad request – The request could not be performed by the server due to bad syntax or other reason in request.
- Code 401 means Unauthorized – Authorization credentials are required or user does not have access to the resource/method they are requesting
- Code 404 means Resource not found – The URI is not recognized by the server
- Code 500 means Server error – Generic something went wrong on the server side
- All are correct
Q.32:
The team which involved in both Production as well Consumption of the reusable assets?
- Central IT
- Developers
- LoB IT
- Experience Engineer
- Architect
No comments:
Post a Comment