QuestionQ1
Managing APIs and integrationsAn organization’s security requirements require centralized, continuous control of authentication and authorization for external applications that invoke web APIs managed on Anypoint Platform.
Which Anypoint Platform feature is the simplest and most maintainable way to meet this requirement?
- A Identify management configured in Access Management
- B Client management configured in Access Management
- C External access configured in API Management
- D Enterprise Security module coded in Mule applications
QuestionQ2
MuleSoft application network conceptsA company is modernizing its legacy systems to speed up access to applications and data while enabling adoption of new technologies. Achieving this business objective depends on unlocking the company’s systems and data, including existing on-premises services that authorized external clients can access. The IT staff’s experience is primarily limited to supporting the legacy systems.
Given the aggressive backlog and project-delivery requirements, the company wants to take a strategic approach during the first phase of its transformation projects by rapidly deploying APIs to Mule runtimes that can scale, connect to on-premises systems, and migrate when necessary.
Following MuleSoft best practices, which MuleSoft runtime deployment option best fulfills the company’s goals for starting its digital-transformation journey?
- A CloudHub runtimes
- B Customer-hosted self-provisioned runtimes
- C Customer-hosted runtimes provisioned by a MuleSoft services partner
- D Runtime Fabric on VMs/bare metal
Community Discussion
QuestionQ3
Designing APIs for reuse and governanceAn organization has developed a large monolithic application over time and is now seeking to move to a microservices architecture. During this transition, it has created several System APIs as Mule applications that expose access to different functionality within the monolithic application. The System APIs are deployed to Mule runtimes on a customer-hosted EC2 instance in AWS.
The System APIs connect directly to a single database used by the monolithic application. Currently, every project must include a Database connector and its connector configuration. There is a future plan to split this database into several smaller data stores.
What MuleSoft-recommended best practice should be used to share the connector and configuration information across the APIs?
- A Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
- B Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database
- C Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
- D Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
Community Discussion
QuestionQ4
Managing APIs and integrationsAn external API often calls an Employees system API to retrieve employee data from a MySQL database. The architect must create a caching strategy that queries the database only when the Employees table is updated; otherwise, it must return a cached response to minimize redundant transactions handled by the database.
What must the architect do to accomplish the caching objective?
- A Use a Scheduler with a fixed frequency set to every hour to trigger an invalidate cache flow.Use an object-store-caching-strategy and the default expiration interval.
- B Use a Scheduler with a fixed frequency set to every hour, triggering an invalidate cache flow.Use an object-store-caching-strategy and set the expiration interval to 1 hour.
- C Use an On Table Row operation configured with the Employees table and call invalidate cache.Use an object-store-caching-strategy and the default expiration interval.
- D Use an On Table Row operation configured with the Employees table, call invalidate cache, and hardcode the new Employees data to cache.Use an object-store-caching-strategy and set the expiration interval to 1 hour.
Community Discussion
QuestionQ5
MuleSoft application network conceptsA large life sciences customer intends to use the Mule Tracing module with Mapped Diagnostic Context (MDC) logging operations to enrich logging in its Mule application and improve tracking by adding more context to Mule application logs. The customer also wants to increase throughput and reduce message-processing latency in its Mule application flows.
After the Mule Tracing module is installed in the Mule application, how should logging be performed in Mule application flows, and what should be changed in the log4j2.xml files?
- A In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.In log4j2.xml files, change the appender’s pattern layout to use %MDC and then assign the appender to a Logger or Root element.
- B In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.In log4j2.xmI files, change the appender’s pattern layout to use the %MDC placeholder and then assign the appender to an AsyncLogger element.
- C In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.In log4j2.xml files, change the appender’s pattern layout to use the % asyncLogger placeholder and then assign the appender to an AsyncLogger element.
- D In the flows, wrap Logger components in Async scopes.In log4j2.xmI files, change the appender’s pattern layout to use the %asyncLogger placeholder and then assign the appender to a Logger or Root element.
Community Discussion
That's the end of the preview
It's free
100% of the questions are free for all users.
No strings attached.
Community Discussion