MuleSoft Certified Platform Architect - Level 1 Practice Exam

A platform architect is choosing an Anypoint deployment topology for a financial-services company with strict data-residency requirements and a 99.99% uptime SLA.

Which deployment topology best fits these constraints?

1. A multi-region Runtime Fabric deployment on customer-managed Kubernetes with active-active configuration, dedicated load balancers, and automated cross-region failover
2. A free-tier CloudHub deployment for cost savings
3. On-premises Mule runtime on a single server
4. CloudHub in a single region with no redundancy

A platform architect must design a disaster-recovery strategy for an Anypoint deployment processing 50,000 API calls per minute.

What DR architecture is most appropriate?

1. Accept that some downtime is inevitable and do not plan for DR
2. An active-passive (or active-active) cross-region setup with automated health monitoring, cross-region data replication, DNS-based failover, documented runbooks, and regular DR testing against measured RTO/RPO targets
3. Rely on MuleSoft’s automatic disaster recovery with no additional configuration
4. Back up application JAR files to a USB drive weekly

A platform architect is defining the environment strategy for a client with 8 development teams that need isolated development, shared testing, and production.

How should the Anypoint Platform environments be structured?

1. A single environment for all teams and purposes
2. One environment per developer
3. Separate environments for Development (per-team or shared), QA/Testing (shared with access controls), Staging (production mirror), and Production, with CI/CD promoting applications through them
4. Only Development and Production, with no testing stages

A platform architect must design how API credentials, secrets, and access are governed across environments on Anypoint Platform.

What approach best meets enterprise security and governance goals?

1. Rely on network firewalls as the sole security mechanism
2. Use the same password across all environments to simplify management
3. Store all secrets in application properties files committed to Git
4. Use Anypoint secure/encrypted properties, integrate an enterprise secrets vault for rotation and audit, enforce TLS everywhere, and apply role-based access control across platform components

A platform architect is sizing infrastructure for a Mule application that must handle 10,000 concurrent API requests with sub-200ms response times.

What capacity-planning approach is best?

1. Use the smallest available instance size to minimize cost
2. Load-test to establish per-worker throughput at the target latency, calculate the number of workers/replicas needed, configure horizontal auto-scaling, and plan ~30% headroom above peak
3. Deploy a single large server and hope it handles the load
4. Size from the vendor’s marketing materials without testing

A platform architect needs a monitoring and alerting strategy for 100 Mule applications running across multiple environments.

What monitoring architecture is most effective?

1. Monitor only production and ignore other environments
2. Use a single shared log file for all applications
3. Multi-layer monitoring: Anypoint Monitoring for application metrics and distributed tracing, infrastructure monitoring for compute/network health, dashboards for business KPIs, and proactive alerting with escalation policies
4. Monitor applications only when users report issues

A Quote-of-the-Day API caches today’s quote. It runs as three CloudHub deployments in three separate regions that must share the cache state.

How should the architect design the shared cache?

1. Rely on each worker’s in-memory cache and accept divergence between regions
2. Use the CloudHub Object Store to persist and share cache state across the regional deployments, giving all three a consistent view of the cached quote
3. Store the cache in a local file on each CloudHub worker
4. Disable caching entirely and recompute the quote on every request

A platform architect must decide when a CloudHub deployment requires a Dedicated Load Balancer (DLB) rather than the Shared Load Balancer.

Which requirement makes a Dedicated Load Balancer necessary?

1. Serving a low-traffic internal API where the default shared endpoint is sufficient
2. Any deployment, since the Shared Load Balancer cannot route HTTPS traffic
3. Needing custom domains/certificates, custom SSL configuration, or mapping rules and two-way TLS — capabilities the Shared Load Balancer doesn’t provide
4. Reducing cost, since a DLB is cheaper than the shared option

A platform architect wants to standardize how APIs are specified, discovered, and reused across teams to grow the application network.

Which Anypoint approach supports design-first APIs and reuse?

1. Design API specifications (RAML/OAS) in Design Center, then publish them to Exchange so teams can discover, reuse, and build against a shared contract
2. Let each team hand-code endpoints with no shared specification
3. Document APIs only in a wiki outside Anypoint Platform
4. Skip specifications and expose database tables directly as APIs

A platform architect is designing the role-based access control model for Anypoint Platform across an enterprise with multiple business units and teams.

What RBAC design best fits an enterprise?

1. Create a single role for all users
2. A hierarchical model: business-group organizations for top-level isolation, environment-specific roles (Developer, Deployer, Admin), team-based permissions via Anypoint Teams, and SSO integration with the enterprise identity provider
3. Manage access through shared credentials per environment
4. Give all users administrator access for simplicity