The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

• A. Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
• B. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
• C. Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
• D. Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation

Refer to the exhibit.
Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices C) Build all API data models using XML schema to drive consistency and reuse across the organization D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

• A. Option A
• B. Option C
• C. Option B
• D. Option D

A system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. A process API is a client to the system API and is being rate limited by the system API, with different limits in each of the environments. The system API's DR environment provides only 20% of the rate limiting offered by the primary environment. What is the best API fault-tolerant invocation strategy to reduce overall errors in the process API, given these conditions and constraints?

• A. In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment; add timeout and retry logic to the process API to avoid intermittent failures; add logic to the process API to combine the results
• B. Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke the system API deployed to the DR environment
• C. Invoke the system API deployed to the primary environment; add timeout and retry logic to the process API to avoid intermittent failures; if it still fails, invoke a copy of the process API deployed to the DR environment
• D. Invoke the system API deployed to the primary environment; add retry logic to the process API to handle intermittent failures by invoking the system API deployed to the DR environment

A manufacturing company has deployed an API implementation to CloudHub and has not configured it to be automatically restarted by CloudHub when the worker is not responding.
Which statement is true when no API Client invokes that API implementation?

• A. No alert on the API invocations is raised but alerts on the API implementation can be raised
• B. Alerts on the APT invocation and API implementation can be raised
• C. Alerts on the API invocations are raised but no alerts on the API implementation can be raised
• D. No alert on the API invocations and APT implementation can be raised

What is a best practice when building System APIs?

• A. Document the API using an easily consumable asset like a RAML definition
• B. Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs
• C. Model all API resources and methods to closely mimic the operations of the backend system
• D. Expose to API clients all technical details of the API implementation's interaction wifch the backend system