Adobe Marketo Engage Certification: Paths, Audience, and Preparation Choices
Adobe Marketo Engage is Adobe’s marketing automation platform for planning, executing, and measuring personalized omnichannel campaigns. Its certification ecosystem is organized around experience level and job role rather than a single universal credential, so marketers, business practitioners, architects, and technical users may need different starting points. This overview explains the credential labels Adobe currently presents, the product knowledge behind them, the preparation resources available through Adobe, and the practical questions to ask before selecting a path. It also highlights where hands-on work with campaigns, CRM synchronization, APIs, and privacy controls matters.
What the Marketo certification ecosystem is designed to assess
The Marketo certification ecosystem is intended for people who already have meaningful experience with Adobe Marketo Engage and want to validate a role-specific level of capability. Adobe’s certification overview is marked “CREATED FOR: Experienced” and directs readers to choose a level and job role before reviewing exam details, study resources, and scheduling options.
Adobe describes Marketo Engage as marketing automation software that streamlines, automates, and measures marketing tasks and workflows. Adobe’s business product page presents the platform as a way to plan, execute, and measure personalized omnichannel campaigns, including batch email, automated nurture, and multi-step campaigns. Those descriptions help explain why the certification catalog is not limited to email creation: the platform spans campaign operations, data, workflow design, integrations, measurement, and administration.
The official certification overview does not present certification as a substitute for product practice. Instead, it connects candidates with exam information, study resources, exam scheduling, the wider certification catalog, and technical training courses. That makes the first decision a role decision: determine which kind of work you want to perform in Marketo Engage, then use Adobe’s current catalog to confirm the matching credential and its live requirements.
Readers should also separate an Adobe certification from informal training or product familiarity. Completing a tutorial can help build skills, but it does not by itself establish which certification is appropriate. Conversely, a certification label should not be treated as proof that someone can design every type of Marketo implementation. The useful value of the ecosystem is its role-and-level structure, supported by the official exam and preparation information.
Which Marketo credentials appear in Adobe’s catalog
Adobe’s Marketo Engage certification overview lists several credential labels across professional, expert, practitioner, master, and architect groupings. The page currently identifies Professional, Certified Professional, Certified Professional - Japanese Digital Marketer, Expert, Business Practitioner, Business Practitioner - Japanese, and Master Architect.
These labels should be read as catalog options, not as a reason to assume that every candidate must complete them in a fixed sequence. The official page tells candidates to select their level and job role; it does not, in the supplied evidence, establish a universal ladder in which every person must earn each listed credential. A sensible progression therefore depends on the work a candidate performs and the credential’s current exam page, rather than on an assumed beginner-to-advanced order.
The Japanese Digital Marketer and Business Practitioner - Japanese entries indicate that Adobe provides Japanese-language options in the catalog. Adobe specifically notes that the Certified Professional - Japanese Digital Marketer certification does not count toward partner requirements. Candidates pursuing a partner-related objective should verify the applicable policy before choosing that option.
The catalog labels also suggest distinct audiences. Professional and Certified Professional options are likely to attract candidates seeking a role-aligned validation of operational skills, while Expert, Business Practitioner, Master, and Architect labels point toward more advanced or specialized responsibilities. That is a practical interpretation of the labels, not an unsupported claim about exam difficulty or mandatory prerequisites. The current Adobe certification page remains the authority for each credential’s intended audience, exam details, and available preparation materials.
For an exact credential name, use Adobe’s official Marketo Engage Certification Overview: https://experienceleague.adobe.com/en/docs/certification/program/technical-certifications/ame/ame-overview
How to choose between a practitioner, technical, and architect direction
Choose the path that matches the decisions you make in Marketo Engage, not merely the feature you use most often. A campaign operator, a business process owner, an integration developer, and an implementation architect may all work in the same instance but need different evidence of competence.
A practitioner-oriented direction is the natural place to investigate if your work centers on campaign planning, segmentation, Smart Campaigns, forms, landing pages, email programs, nurture, scoring, operational workflows, and performance analysis. Adobe’s product documentation lists capabilities such as the Form Editor, Landing Page Editor, Smart Campaigns, Dynamic Chat, Native Interactive Webinars, the Email Editor, segmentation, Predictive Content, integrations, workflow tools, person scoring, in-CRM dashboards, program analysis, and target account management. A candidate whose daily work involves configuring and measuring these functions should compare the practitioner-oriented entries in the official catalog.
A business-focused direction deserves attention when your responsibility is to translate marketing objectives into Marketo operating processes. This can include defining lifecycle stages, agreeing on lead-handling rules, coordinating with sales, deciding how programs should be measured, and establishing governance for reusable assets. A business practitioner does not necessarily need to be the person writing integrations, but should understand how the platform’s data and workflows support business outcomes.
An architect direction is more suitable for people responsible for the shape of a broader implementation. That may involve data models, system boundaries, CRM relationships, integration patterns, access, operational governance, and the effect of platform limits on solution design. The supplied evidence does not define the Master Architect credential’s requirements, so candidates should not infer a specific prerequisite or project requirement from the title alone. Instead, review Adobe’s current architect exam page and compare it with the work you actually perform.
A technical direction is relevant when your Marketo responsibilities extend into APIs, custom integrations, data movement, or administrative controls. Adobe’s REST API documentation identifies Lead Database APIs for person records and related objects and Asset APIs for marketing collateral and workflow records. That technical scope is materially different from simply building an email or Smart Campaign. If you maintain an integration, troubleshoot API responses, or design automated data exchanges, those areas should be part of your readiness review even if the certification title is not explicitly called “developer.”
If your role crosses categories, choose the credential that best reflects your primary accountability and use the other domain as supporting preparation. For example, a marketing operations lead may need practitioner knowledge as the core and CRM synchronization knowledge as a supporting area. An integration specialist may need a technical focus while still understanding campaigns, assets, and the data those integrations serve.
A quick role-matching exercise
Write down the last several Marketo tasks for which you were accountable, then group them under campaign operations, business process, administration, data integration, or architecture. The largest group is a useful starting signal, but it is not an official eligibility rule.
Next, identify the consequence of an error in that work. If the main risk is an incorrectly targeted campaign, campaign logic and segmentation deserve priority. If the risk is a broken data exchange, API behavior, field mapping, authentication, and CRM synchronization deserve more attention. If the risk is noncompliant tracking or mishandled personal data, privacy configuration and request handling belong in the preparation plan.
Finally, compare that work profile with the level and job-role choices on Adobe’s certification page. If two options still seem plausible, select the one whose exam description most closely matches your accountability, rather than choosing solely by the credential title.
The product knowledge common to many Marketo paths
Most Marketo candidates benefit from a broad product foundation before specializing. Adobe’s own introduction to Marketo Engage says users do not need to learn every feature and can use the pieces that suit their needs. For certification selection, however, knowing your intended scope matters: a narrow campaign role and an implementation role require different breadth.
Start with the platform’s operating model. Understand how people enter the database, how attributes and activities support segmentation, how programs and assets are organized, and how Smart Campaigns automate actions. Then connect those building blocks to measurement: what the organization wants to observe, which data is trusted, and how campaign performance is interpreted.
CRM synchronization is another important boundary. Adobe documents that Marketo can synchronize with Salesforce throughout the day, with each sync taking some time and then pausing for 5 minutes before starting again. The synchronization is bidirectional for leads, contacts, and Salesforce campaigns; other listed syncs are from Salesforce to Marketo only. Adobe also states that the first sync may take hours or days because the database is copied, while later syncs generally process changed data.
These details matter to certification preparation because a candidate should be able to reason about the relationship between Marketo and the connected CRM, not simply memorize that an integration exists. Practical questions include which system owns a field, how a change moves between systems, what access the Salesforce credentials provide, and how a campaign depends on synchronized data.
Privacy is part of responsible platform use. Adobe documents that Marketo privacy settings can honor or ignore browser Do Not Track settings, support a site-specific opt-out cookie, or use anonymized-IP tracking. Those choices can affect the value and functionality of particular features, so candidates working with web tracking should understand the configuration implications rather than treating consent as a purely theoretical topic.
Adobe also documents privacy requests for access and deletion through the Privacy Service UI and API. For Marketo Engage, those requests apply to users onboarded to the Adobe Identity Management System or using another specified Experience Cloud product already on that system. This qualification is important: it means candidates should verify the organization’s identity and product setup before assuming that a particular request workflow applies to every Marketo database.
The core product foundation is therefore broader than sending communications. It includes data, automation, integration, measurement, administration, and privacy. The relative weight of each area should follow the chosen role and Adobe’s current exam outline.
Use the official product documentation as a coverage map
Adobe’s Marketo Engage introduction is useful for identifying the platform’s feature families, while the CRM synchronization, REST API, privacy, and release-note pages provide deeper operational context. Use them to build a coverage map with three columns: what the feature does, what decision the user must make, and what can go wrong if it is configured incorrectly.
This approach is more useful than collecting isolated definitions. For example, instead of recording only that Marketo has Smart Campaigns, connect Smart Campaigns to audience qualification, flow actions, timing, and measurement. Instead of recording only that Marketo integrates with Salesforce, connect that integration to ownership, direction of synchronization, credentials, and timing.
Adobe’s overview of Marketo Engage is available at https://experienceleague.adobe.com/en/docs/marketo/using/getting-started/what-is-adobe-marketo-engage. The Salesforce synchronization documentation is at https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/crm-sync/salesforce-sync/understanding-the-salesforce-sync.
When API and integration knowledge should shape your preparation
Treat API preparation as central when your target role involves system integration, data operations, or technical administration. Treat it as supporting knowledge when you are a campaign practitioner who must understand the impact of an integration without building one.
Adobe’s REST API documentation says the API provides remote access to many Marketo capabilities, including creating programs, importing leads in bulk, and controlling an instance at a detailed level. It divides the REST APIs into Lead Database APIs, which interact with person records and related object types such as Opportunities and Companies, and Asset APIs, which interact with marketing collateral and workflow-related records.
Technical candidates should learn the difference between a successful HTTP exchange and a successful Marketo operation. Adobe states that when a call contains an error, the API typically still returns HTTP status code 200; the JSON response instead contains a success member with a value of false and an errors array. A preparation plan that checks only HTTP status codes is therefore incomplete.
The documented operating limits are also relevant to solution design. Each subscription is allocated 50,000 API calls per day, each instance is limited to 100 API calls per 20 seconds, and each instance allows a maximum of ten concurrent API calls. Standard API calls have a maximum URI length of 8 KB and a maximum body size of 1 MB, while bulk API calls support a maximum body size of 10 MB. These are product facts from the supplied documentation, not a guarantee that a certification exam will test every limit.
Adobe’s release notes state that the Marketo SOAP API was deprecated and no longer available as of July 31, 2026, and that new development should use the REST API. Candidates maintaining older integrations should therefore distinguish legacy knowledge from the current documented direction. Adobe’s release notes also identify a deprecation of the access_token query parameter and direct new and existing integrations toward the Authorization header. Check the current documentation before building a study plan around an older integration pattern.
The release notes also record a REST API Merge Leads limit: calls containing more than 25 IDs in the leadIds parameter result in a 1080 error code and are skipped. Jobs requiring the merger of more than 25 records into one should be split into multiple jobs. This is a good example of why technical readiness involves handling constraints and failure conditions, not just knowing endpoint names.
The API documentation is at https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api. Use the current release notes at https://experienceleague.adobe.com/en/docs/marketo/using/release-notes/current to check whether the behavior and availability relevant to your work have changed.
A practical technical readiness check
Before choosing a technical or architect-oriented path, confirm that you can explain an integration from end to end: how credentials are provisioned, how requests are authenticated, which object family is involved, how records are identified, how errors are detected, how limits affect throughput, and how the result is monitored.
Adobe’s REST setup documentation describes an admin-led workflow involving an API user, an API role, a LaunchPoint service, client credentials, an access token, and the REST endpoint. You should not practice against production data merely to gain familiarity. Use an authorized environment and follow your organization’s security process.
A strong readiness signal is the ability to diagnose a realistic failure without guessing. For example, you should be able to investigate a response whose HTTP status appears successful but whose JSON success value is false, and you should know where to look for error details. You should also recognize that a large merge operation may need to be divided rather than repeatedly retried unchanged.
How release notes and edition differences affect certification choices
Use current release notes to protect your preparation from stale product assumptions, but do not treat every release-note item as an automatic exam objective. Adobe’s current Marketo Engage release notes warn readers to check their edition for feature availability and state that release features and dates are subject to change.
This matters when a candidate works in an environment with a different edition, rollout status, or enabled capability. A study resource may describe a function that is unavailable in the candidate’s subscription, while a day-to-day configuration may reflect an older interface or integration pattern. The right response is to verify the feature in Adobe’s current documentation and then compare that information with the certification exam description.
Release notes are especially valuable for technical candidates because they identify deprecations, changed response formats, API limits, and migration instructions. They are also useful to administrators and practitioners when interface changes affect navigation or when a new capability changes how a workflow is configured. However, reading release notes from beginning to end is not a substitute for learning the underlying product model.
Build a short update check into your preparation. Confirm the current exam page, review the latest relevant documentation, note any deprecation or edition limitation that affects your work, and avoid relying on copied summaries whose publication date or product version is unclear. Adobe’s official certification overview is the place to connect the current credential choice with exam details and study resources.
A preparation approach that matches the chosen credential
Prepare in layers: establish product fundamentals, practice the tasks associated with your role, then test your ability to make decisions under realistic constraints. This approach is more dependable than memorizing feature names or relying on unauthorized question collections.
Begin with Adobe’s official certification overview. It directs candidates to exam details, study resources, scheduling, the certification catalog, and technical training courses. Use the chosen credential’s current page to identify the published domains and any stated requirements. The supplied evidence does not provide universal prerequisites, exam durations, prices, passing scores, or renewal policies, so those details should be taken only from the live Adobe page when you are ready to schedule.
Next, work through the relevant product documentation. A practitioner should be able to create and troubleshoot campaign logic, work with assets and audiences, interpret program behavior, and connect actions to measurement. A business practitioner should be able to explain process ownership, lifecycle decisions, collaboration with sales, and governance. An administrator or technical candidate should add access, synchronization, API, privacy, and operational troubleshooting to that foundation.
Practice with decisions rather than flashcard prompts. Ask what should happen when a person qualifies for a campaign, which data source should be authoritative, how an audience should be excluded, how an integration error would be identified, or how a privacy request should be routed. Then confirm the answer in official documentation. This helps reveal gaps in reasoning and keeps preparation tied to actual Marketo work.
For integration-heavy roles, include small authorized exercises such as reviewing a request structure, interpreting a JSON response, checking the success member and errors array, and tracing a record from source system to Marketo. For privacy-related roles, review the identity and eligibility conditions Adobe documents for Privacy Service requests. For campaign roles, build a complete but non-production workflow that includes audience definition, content, timing, operational safeguards, and measurement.
Use training and tutorials to fill gaps, but assess whether they reflect the current product version and your chosen credential. Adobe’s Marketo introduction points users toward tutorials and says they can begin learning before setup is complete. That makes tutorials a useful entry point, but an experienced certification candidate should progress from guided learning to independent configuration and troubleshooting.
Do not confuse familiarity with readiness. You may recognize a term without being able to choose among competing configurations, explain an integration consequence, or identify a privacy limitation. Your final review should therefore include both recall and applied reasoning.
Build a role-based study matrix
Create a matrix with the following rows: campaign execution, data and segmentation, assets and programs, CRM synchronization, administration and access, APIs and integrations, privacy, measurement, and release awareness. Mark each row as primary, supporting, or outside scope for the credential you are considering.
For every primary row, write one task you can perform and one failure you can diagnose. For every supporting row, write the boundary you need to understand. This prevents a campaign-focused candidate from spending all preparation time on API mechanics while still ensuring they understand how integrations affect campaign data.
Keep official requirements separate from your own readiness targets. The exam page may specify a domain or experience expectation; your matrix is a practical method for deciding whether you can work independently in that domain. Neither should be presented as the other.
What experience signals that you may be ready
Readiness is strongest when you can explain why a Marketo configuration works, not only how to click through it. The most useful signals are repeated responsibility, exposure to consequences, and the ability to troubleshoot without relying on guesswork.
For a campaign-oriented path, useful experience may include building or reviewing programs, managing segmentation, configuring Smart Campaign logic, coordinating assets, analyzing outcomes, and handling exceptions. You should understand how a change to audience criteria or flow logic can alter who receives an action and how that result is measured.
For a business practitioner path, readiness includes being able to turn a marketing process into clear Marketo requirements. You should be comfortable discussing lifecycle definitions, handoffs, field ownership, campaign governance, and the difference between a requested feature and a sustainable operating process.
For an administration or technical path, look for experience with permissions, users, services, integrations, data quality, and operational monitoring. Adobe’s API documentation notes that admin privileges are needed for the setup workflow it describes. That is a reminder that technical work in Marketo includes controlled administration, not just code.
For an architect-oriented direction, readiness means seeing interactions across the system. You should be able to anticipate how data design affects segmentation, how CRM synchronization affects ownership, how API limits affect integration throughput, and how privacy choices affect tracking and request handling. The official evidence supplied here does not state a required project history for Master Architect, so use these as practical indicators rather than formal eligibility rules.
A gap is not a reason to abandon certification. It is a reason to choose a more appropriate starting point, gain supervised experience, or narrow the preparation scope. If your work is mostly content production but you are considering an architecture credential, first identify the missing exposure instead of assuming that reading more summaries will provide it.
How different audiences can select a sensible starting point
Marketing practitioners should begin by matching their daily campaign responsibilities to the professional, certified professional, or business practitioner entries in Adobe’s catalog. Compare the official role descriptions and exam domains, then prioritize hands-on work with the features your organization actually uses.
Marketing operations professionals should look beyond email assembly. Data governance, lifecycle operations, CRM relationships, program structure, scoring, measurement, and troubleshooting may all be relevant. A practitioner credential may fit a configuration-heavy role, while a business practitioner option may better reflect process ownership. The correct choice depends on Adobe’s current role definitions and your accountability.
CRM administrators and integration specialists should investigate the technical and architect-oriented options while reviewing the REST API and Salesforce synchronization documentation. Do not choose solely because an option sounds advanced. Confirm that the credential’s published scope aligns with your actual responsibility for authentication, data movement, limits, error handling, and system design.
Consultants and implementation partners should distinguish personal learning goals from partner requirements. Adobe’s note about the Certified Professional - Japanese Digital Marketer credential not counting toward partner requirements is a concrete example of why the intended use of a credential matters. Verify partner policy directly rather than assuming that any Marketo certification satisfies an external requirement.
Managers and team leads can use the catalog to assign complementary paths instead of sending every employee toward the same exam. A campaign specialist, business process owner, and integration specialist may need overlapping fundamentals but different depth. A team plan can therefore cover the ecosystem more effectively by matching credentials to responsibilities.
People new to Marketo Engage should first build product familiarity and confirm which work they want to perform. Adobe says Marketo Engage includes tutorials that can be started before setup is complete, so an introductory learning phase can precede a certification decision. Do not present a beginner tutorial as proof of eligibility for an experienced certification path; use it to determine whether the platform and role are a sensible fit.
Privacy and governance should not be an afterthought
Treat privacy and governance as part of Marketo competence whenever your role touches tracking, forms, audience data, or data-subject requests. These concerns influence configuration and operational decisions, not just legal documentation.
Adobe documents three relevant privacy-setting approaches: honoring or ignoring browser Do Not Track settings, allowing a site-specific opt-out cookie, and tracking with an anonymized IP. The documentation explains that these methods may affect Marketo’s value and functionality in specific areas. A candidate should therefore understand the trade-off created by a setting, identify who owns the decision, and know where to verify the implementation.
For Privacy Service requests, Adobe states that access and deletion requests for Marketo Engage apply only to users onboarded to Adobe Identity Management System or using another specified Experience Cloud product already on that system. The documented setup requires an IMS Org ID and the email address of the person whose data is involved. The IMS Org ID is described as a 24-character alphanumeric string appended with @AdobeOrg.
Those details do not turn certification preparation into legal advice. They do show why candidates should learn the documented workflow, scope, identity requirements, and escalation path. If your organization has a privacy office or data protection process, understand how Marketo actions fit within it and do not test requests against real individuals without authorization.
The official privacy references are https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/administration/settings/understanding-privacy-settings and https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/core-marketo-concepts/miscellaneous/privacy-requests.
Questions to answer before booking a Marketo certification
Confirm the exact credential name and job role on Adobe’s current certification page before booking. Similar-sounding labels can represent different audiences, and the supplied evidence does not establish that every listed credential has the same requirements or progression rules.
Check the current exam details, including any stated experience expectations, domains, delivery information, scheduling instructions, and policies. Do not rely on old pages or third-party summaries for prices, dates, renewal, exam status, or prerequisites when those details can change.
Ask whether the credential serves your immediate objective. Are you validating campaign execution, business process knowledge, technical administration, integration design, or architecture? If the answer is unclear, the role choice is not ready.
Check feature availability in your edition. Adobe explicitly tells readers to check their Marketo Engage edition for feature availability in the current release notes. A feature that is central to someone else’s implementation may not be available in yours.
Check whether the language option has an external limitation. Adobe notes that the Certified Professional - Japanese Digital Marketer certification does not count toward partner requirements. Verify any partner or employer policy independently.
Check whether your preparation environment is authorized and representative. Avoid using production data for practice, confirm access permissions, and make sure your exercises reflect the integrations and edition relevant to your work.
Check how you will maintain knowledge after certification. Adobe’s release notes document changes to interfaces, APIs, authentication patterns, and limits. A certification decision should include a plan to follow official product updates, especially for technical responsibilities.
Finally, ask what evidence would persuade you that you are ready. Good evidence might include completing role-relevant configurations, explaining design choices, diagnosing errors, and handling documented constraints. Passing should never be framed as guaranteed by memorization or unauthorized materials.
Why unofficial exam dumps are a poor preparation strategy
Exam dumps are not a reliable way to build Marketo competence and should not be treated as a guarantee of passing. They can be inaccurate, outdated, unauthorized, or disconnected from the product behavior your role requires.
Marketo changes through release updates, edition-specific availability, API deprecations, interface changes, and revised operational limits. A copied question set can therefore teach a candidate to recall an answer that no longer fits the documented product. The risk is greater for technical candidates, because an incorrect assumption about authentication, error handling, synchronization, or limits can damage a real implementation.
Use Adobe’s certification overview to find official exam details, study resources, scheduling information, and technical training. Use Adobe’s product documentation to verify behavior, and use controlled hands-on practice to test whether you can apply it. This combination supports durable skill rather than answer memorization.
A responsible preparation plan also respects credential integrity. Do not seek leaked questions or present memorized content as product understanding. The goal of an independent certification path is to help you choose a role that matches your work and demonstrate that capability through the vendor’s official process.
A practical decision path for your next step
Start with your job objective, then validate it against Adobe’s current catalog. If you operate campaigns and assets, investigate the professional or certified professional choices that match that work. If you own marketing processes and cross-team requirements, compare the business practitioner direction. If you manage integrations, data access, APIs, or solution structure, examine the technical and architect-oriented options.
After selecting a candidate path, read its official exam information and create a role-based coverage matrix. Use Adobe’s Marketo introduction for product breadth, the Salesforce documentation for synchronization behavior, the REST API guide for technical scope, and the privacy documentation for tracking and request boundaries.
Then test readiness in an authorized environment. Build or review workflows, trace data movement, interpret results, investigate failure conditions, and explain the governance behind your choices. When you find a gap, return to the relevant Adobe documentation rather than filling it with an unsupported assumption.
Before scheduling, confirm every time-sensitive detail on Adobe’s live certification page. The supplied evidence identifies the ecosystem and the preparation channels, but it does not establish universal prices, durations, passing scores, renewal terms, or prerequisites. Those should be treated as current-policy questions for Adobe, not guessed from the credential label.
The most sensible Marketo certification path is therefore the one that aligns three things: the work you perform, the level and role Adobe assigns to the credential, and the product areas you can demonstrate through practice. That alignment is more useful than choosing the most advanced-sounding title or treating certification as a generic badge.
Conclusion
Adobe Marketo Engage offers a role- and level-oriented certification ecosystem for experienced users rather than one undifferentiated credential. Begin by deciding whether your center of gravity is campaign operations, business process, administration, integration, or architecture. Then confirm the matching Adobe credential, study its official exam information, and prepare with product documentation plus authorized hands-on practice. Pay particular attention to CRM synchronization, APIs, privacy, edition availability, and release changes when they affect your role. For current credential names, exam details, study resources, and scheduling, use Adobe’s Marketo Engage Certification Overview: https://experienceleague.adobe.com/en/docs/certification/program/technical-certifications/ame/ame-overview.
