Salesforce-MuleSoft-Platform-Architect Practice Test
Salesforce Spring 25 Release 152 Questions
The asset version 2.0.0 of the Order API is successfully published in Exchange and configured in API Manager with the Autodiscovery API ID correctly linked to the
API implementation, A new GET method is added to the existing API specification, and after updates, the asset version of the Order API is 2.0.1,
What happens to the Autodiscovery API ID when the new asset version is updated in API Manager?
A. The API ID changes, but no changes are needed to the API implementation for the new asset version in the API Autediscovery global element because the API ID is automatically updated
B. The APL ID changes, so the API implementation must be updated with the latest API ID for the new asset version in the API Autodiscovery global element
C. The APLID does not change, so no changes to the APT implementation are needed for the new asset version in the API Autodiscovery global element
D. The APL ID does not change, but the API implementation must be updated in the AP] Autodiscovery global element to indicate the new asset version 2.0.4
C. The APLID does not change, so no changes to the APT implementation are needed for the new asset version in the API Autodiscovery global element
Explanation:
The Autodiscovery API ID remains stable across minor/patch version updates (e.g., 2.0.0 → 2.0.1) because:
The ID is tied to the API contract (API Manager), not the asset version.
Only major version changes (e.g., 2.0.0 → 3.0.0) require a new API ID.
Why other options are wrong:
(A/B): API ID does not change for minor updates.
(D): No need to update the implementation—Autodiscovery automatically tracks versions.
This ensures seamless upgrades without breaking existing integrations.