Atlassian Certification Exams
Atlassian Certification Exams: Overview and Strategic Value
What Atlassian certifications actually prove about your skills
Okay, real talk.
If you're working with Atlassian tools (or want to), you've probably wondered whether getting certified actually makes any sense. I mean, we all know that one person who can configure Jira workflows in their sleep but doesn't have a single cert, right? But here's the thing: Atlassian certification exams validate something employers actually care about, and it's surface-level clicking around or following tutorials you found on YouTube.
These certifications test your ability to handle system administration tasks, configure projects properly, manage governance and security, and implement automation that doesn't break everything the second it goes live. The exams focus heavily on practical scenarios you'd encounter managing real Jira or Confluence instances. Not gonna lie, the theoretical stuff is there too, but Atlassian really emphasizes hands-on competency over just memorizing documentation word-for-word.
What you're demonstrating is tangible. When you pass one of these exams, you're showing you can administer permissions schemes without locking everyone out (including yourself), set up workflows that make sense for actual teams instead of creating bureaucratic nightmares, and understand the security implications of your configuration choices. That's worth something in today's market.
How the certification space shifted (and why it matters in 2026)
Everything changed around 2020.
The Atlassian certification ecosystem went through a massive transformation starting then because the company pivoted hard toward Cloud-first certifications. Honestly, that's where the market moved regardless of what old-school admins wanted. By 2026, the split between Cloud and Data Center/Server certifications is super clear, and you need to understand which path matches your work environment before dropping money on the wrong exam.
The older Server-focused exams are still around, like ACP-600 for Project Administration in Jira Server, but most organizations are either already on Cloud or planning their migration whether their IT teams like it or not. This means the Cloud-specific certifications like ACP-120 for Jira Administration for Cloud and ACP-620 for Managing Jira Projects for Cloud carry way more weight in the job market now. Especially if you're looking at positions with companies that aren't stuck in 2018.
Some companies still run Data Center. They've got compliance or control reasons that make sense, which is why ACP-610 for Managing Jira Projects for Data Center and Server remains relevant in specific industries. But the certification program evolution clearly signals where Atlassian wants everyone to go. Fighting that tide seems exhausting.
I remember when Server was the only option anyone talked about. You'd go to Atlassian Summit and every session was about on-premise deployments and how to optimize your hardware for peak performance. Now those same conference rooms are full of Cloud migration stories and disaster recovery tales. The shift happened faster than anyone predicted.
Who actually needs these certifications
It breaks down cleanly.
The target audience isn't monolithic, which confuses some people. System administrators who manage the entire Atlassian instance need different skills than project administrators who just configure individual projects for their teams. Then you've got organization administrators dealing with user management and billing at the top level, plus consultants who need to prove expertise to clients before anyone signs a contract.
If you're a system admin, the ACP-100 Jira Administrator exam is probably where you start. It covers the foundational administration concepts that apply regardless of deployment type, though some details shift between Cloud and Data Center. Project admins might jump straight to something like ACP-620 or ACP-610 depending on their environment and whether they've already got practical experience under their belt.
The ACP-520 Atlassian Cloud Organization Admin certification targets a specific role that didn't really exist in the Server days. It's completely different from traditional admin work. It's all about managing multiple products, user provisioning, security policies, and cross-product governance at an organizational scale. If you're responsible for an entire Atlassian Cloud site with hundreds of users across different departments, this one proves you know what you're doing and won't accidentally break authentication for everyone.
Consultants need certifications for different reasons entirely. They're selling expertise to clients who want proof upfront that they're not just smooth talkers. Having that ACP designation on your LinkedIn means you can charge more and win contracts easier. The ROI is pretty straightforward there.
Why employers care about certified professionals right now
Market demand is high.
Companies implementing or migrating to Cloud need people who already understand the platform's details in 2026, not someone who'll spend months fumbling through the admin console. They don't want to waste time and money while someone figures out permission schemes through trial and error that could expose sensitive data or lock critical users out of projects they need access to right now.
The Cloud transformation specifically created this demand spike that we're still riding. Organizations moving from Server or Data Center to Cloud discovered the administration model is different enough to cause real problems. I mean, it's a lift-and-shift situation like some vendors promised. A certified professional who understands Cloud-specific concepts like organization-level settings, product access, and the limitations compared to Data Center can save a company from configuration disasters that cost thousands in downtime.
Certifications align pretty well with actual work. Atlassian designed the exams around admin tasks you perform regularly. You're tested on things like setting up notification schemes, configuring issue security, managing custom fields without creating technical debt, and implementing workflow post-functions that don't create infinite loops. These aren't theoretical exercises invented by test writers. They're what you do in the admin console every week if you're doing your job properly.
The credibility factor you can't ignore
Certification is proof. Period.
When you're dealing with stakeholders who don't know you yet, they need something concrete. I've seen this play out with consultants especially. A client doesn't know if you're actually good or just confident and charming during the sales call. That digital badge showing you passed a proctored exam with scenario-based questions gives them something they can verify independently without relying on your word or vague references.
For in-house administrators, certifications help during performance reviews and promotion discussions when you're advocating for yourself. Your manager might not fully understand what you do all day in the Atlassian admin console (honestly, most don't), but they understand certifications and professional development. It's a shorthand for "this person invested time learning best practices and passed an industry-standard assessment instead of just winging it based on Google searches."
The ACP designation carries weight. The Atlassian Certified Professional recognition spans different markets and industries more than you'd expect. Tech companies obviously recognize it, but I've seen financial services firms, healthcare organizations, and government agencies specifically list Atlassian certifications in job postings as either required or strongly preferred. The global recognition is real and expanding.
Understanding prerequisites and when you're ready
Atlassian recommends experience levels. They're not hard requirements, technically.
For something like ACP-100, they suggest six months of hands-on Jira administration, and that's probably accurate for most people. You could maybe pass it with less experience if you study hard and have a strong technical background, but you'd struggle with the scenario-based questions without real-world context that only comes from actually administering an instance where users complain when you break things.
The platform-specific exams like ACP-120 and ACP-620 assume you already understand Jira concepts and are just learning the Cloud-specific implementations. They won't teach you what a workflow is from scratch. If you're completely new to Atlassian tools, jumping straight to a Cloud project administration exam would be rough and probably a waste of your exam fee.
Here's what nobody tells you upfront: the difference between passing and actually being competent comes down to hands-on practice with actual instances where you've got admin access. Reading documentation helps (obviously), but you need to break things in a test environment and figure out why your workflow transition doesn't work or why users can't see certain projects even though the permissions look correct. That troubleshooting experience is what separates people who memorized answers from people who actually know what they're doing.
Integration with the broader ecosystem matters more than you think
These certifications don't exist in isolation.
They prove you understand how Jira integrates with Confluence, how Bitbucket fits into the picture for development teams following modern DevOps practices, and increasingly how third-party marketplace apps extend functionality without creating security vulnerabilities or performance problems. The exams test your understanding of the ecosystem as a connected platform, not just individual products you manage separately.
You'll see questions about linking Confluence spaces to Jira projects properly, understanding how automation rules can span multiple products to create better workflows, and managing permissions consistently across your Atlassian environment so users don't have conflicting access rights. This approach reflects how organizations actually use these tools, not as standalone products they licensed separately but as an integrated platform where everything connects and needs coordination.
What happens after you pass
Certification maintenance gets overlooked.
People forget this when considering whether to pursue these exams initially. Atlassian certifications don't expire in the traditional sense with hard cutoff dates, but the platforms evolve constantly and your knowledge becomes outdated faster than you'd think. Your certification becomes way less relevant if you earned it on Server concepts and everyone's moved to Cloud with completely different administration models.
Staying current means periodically taking updated versions of exams as Atlassian releases them to reflect platform changes. The Cloud platform gets new features quarterly. Some minor, some game-changing. Best practices shift as Atlassian learns from customer implementations. What worked perfectly in 2024 might be deprecated or considered an anti-pattern by 2026.
Investment perspective: costs and returns
Exam costs vary. Generally a couple hundred dollars per attempt.
Study time depends heavily on your existing experience. Anywhere from 20 hours if you're already doing the job daily and just need to formalize knowledge, to 60+ hours if you're learning from scratch without any Atlassian background. Don't underestimate that time investment when you're planning around a full-time job and other commitments.
The return on investment shows up differently depending on your situation. For consultants, it's immediate and measurable. You can charge higher hourly rates and win more contracts when competing against non-certified rivals. For in-house admins, it's about career progression and salary negotiations when you're pushing for that promotion or raise. The certification gives you use during compensation discussions because you have third-party validation of your skills rather than just your manager's subjective opinion of your performance.
Organizations value certified professionals. They reduce risk, frankly. Someone with an ACP-520 certification managing your Cloud organization is less likely to misconfigure security settings that expose sensitive data or accidentally delete critical configuration that takes days to rebuild. That risk reduction has real monetary value to companies even if it's hard to quantify precisely on a spreadsheet. Fewer incidents means fewer emergency fixes and less downtime that impacts revenue.
Atlassian Certification Paths: Role-Based Learning Journeys
Atlassian certification exams: overview
Look, Atlassian certification exams are basically proof you've got actual skills, not just vibes or "I binged some YouTube tutorials and now I'm totally a Jira expert." They confirm you can legitimately configure production environments, untangle those nightmare permission scenarios that make everyone panic, and make architectural decisions that won't completely torpedo an instance first thing Monday morning when everyone's caffeinating.
I actually like the role-based structure. Most companies already divide responsibilities this exact way: there's the platform owner, the project delivery person handling mechanics and sprint logistics, and the enterprise governance lead managing products, users, security protocols, and billing nightmares. Atlassian certification paths mirror that organizational reality, so you stop randomly picking whichever badge "feels right" and instead choose a path aligning with your current responsibilities, or honestly where you wanna be next year when you're sick of being the accidental admin nobody officially recognized.
Cloud versus Data Center/Server matters. A lot.
The Jira Cloud versus Data Center distinction isn't cosmetic branding. It fundamentally shifts what concepts you're tested on and what systems you're touching daily, especially around user provisioning workflows, app management constraints, and customization boundaries that either exist or don't.
Atlassian certification paths (role-based)
Three primary tracks appear in actual companies way more than folks acknowledge: Administrator, Project Administrator, and Organization Administrator. Different impact radius. Different stakeholders breathing down your neck. Completely different flavors of crisis.
How do you figure out your path? Honestly, ask yourself one simple question: when systems break, what problems are you personally expected to resolve without immediately escalating to someone else? If that answer includes "global configuration settings, directory integrations, permission schemes affecting everyone, workflows spanning multiple teams," you're squarely on the Jira Administrator path. If it's "this specific team's project setup, their boards, sprint reports," that's Jira Project Administration territory. If you're handling "cross-product access controls, organizational security policies, billing reconciliation, enterprise-wide governance," you're living in Atlassian Cloud Organization Admin land.
Quick gut-check framework. Not flawless. Pretty useful though.
- Jira Administrator track: you effectively own the entire instance, people constantly ping you about confusing permission schemes and bizarre workflow behavior, you regularly get pulled into security audit meetings, and you really care about performance metrics when users vaguely complain "Jira feels slow" without providing literally any helpful details whatsoever.
- Jira Project Administration track: you're embedded with delivery teams daily, managing boards, configuring sprint setups, tweaking quick filters, adjusting issue type schemes within project boundaries, and you're perpetually translating "our process" into Jira configurations without accidentally creating an unusable labyrinth that frustrates everyone.
- Cloud Organization Admin track: you're positioned closer to IT operations, identity management systems, compliance frameworks, and cost optimization initiatives, and stakeholders regularly ask you pointed questions like why external contractors still retain full system access three months after their engagement ended.
Jira administrator path (admin-focused)
This path represents deep technical expertise for system-wide configuration and architecture. Focus areas are the components that'll either maintain Jira's integrity for years or quietly transform it into a permission nightmare: user management hierarchies, permission models, system schemes, workflow design, custom field governance.
Short sentence here. Massive implications.
Target roles are pretty straightforward: Jira Administrators, System Administrators, Technical Administrators with platform responsibilities. If you're already the person who intuitively understands why combining a permission scheme with an issue security scheme can mysteriously make critical issues "vanish" for half your organization, you're already performing this job. You might just lack the official title or recognition.
For Data Center/Server environments, the foundational certification is ACP-100 (Jira Administrator Exam). For Cloud deployments, the parallel credential is ACP-120 (Jira Administration for Cloud). And yeah, people constantly ask "What is the difference between ACP-100 and ACP-120?" because they assume it's essentially identical content with superficial rebranding, but Cloud heavily emphasizes org-managed project concepts and Atlassian-imposed architectural constraints, while Server/DC expects you to deeply understand the platform configuration levers you directly control, including the infrastructure elements affecting scalability and system stability.
Skills developed here are really career-making. Troubleshooting complex issues. Performance optimization under load. Security configuration across enterprise contexts. I mean, literally anyone can slap in a custom field, but accurately diagnosing why specific automation rules are creating load spikes, or why group membership synchronization changes aren't propagating as expected, or why one particular workflow transition condition blocks only a single issue type in one project following a scheme modification.. that's the gap between junior admin and "we desperately need you on this incident bridge right now."
Career progression typically flows: junior admin, admin, senior admin, then advancing into platform architect positions, or pivoting into Atlassian consulting if you really enjoy variety and can handle constant context switching without completely losing your sanity.
Jira project administration path (project-focused)
Project-level configuration and direct team support is where tons of people initially start because it's intimately connected to delivery work. It's also where you discover how Jira can really help teams, or absolutely hurt them, depending entirely on whether you overbuild configurations.
Focus areas include project setup fundamentals, board configuration mechanics, workflow customization within boundaries, and team management practices. Reporting naturally shows up too, because literally every stakeholder wants their own dashboard, and realistically half of them want dashboards that directly contradict what the other half requested. The thing is, this track is what I'd recommend to Scrum Masters and Team Leads who continuously get designated as the "Jira person" during ceremonies, plus Project Managers wanting reduced dependency on centralized admin teams.
For Data Center/Server, you'll encounter ACP-600 (Project Administration in Jira Server) and also ACP-610 Managing Jira Projects for Data Center and Server as an alternative pathway depending on which version and scope your organization still operates. For Cloud, it's ACP-620 (Managing Jira Projects for Cloud Exam). I won't pretend the naming convention is intuitive. It absolutely isn't. Carefully read the official exam pages and map them against your actual daily responsibilities.
Skills developed here lean more delivery-facing: implementing agile methodologies in Jira without making teams actively hate using Jira, building sustainable collaboration patterns around boards and backlog management, and producing reporting that doesn't accidentally misrepresent reality. Career progression often moves from team coordinator to program-level ownership responsibilities, and in larger enterprises it can evolve into enterprise project management, where your Jira architectural choices directly affect multiple teams and portfolio-level rollups.
Side note: I once watched a project admin accidentally delete a shared board filter that 40 people had bookmarked. The Slack explosion was legendary. Turns out everyone had customized their personal copies anyway and nobody was actually using the original filter, but the perceived crisis was real enough that we had to send a company-wide "calm down" email. Teaches you fast that communication matters as much as technical skill.
Atlassian cloud organization admin path (org-wide governance)
This one covers enterprise governance and cross-product management, and honestly it's more "IT control plane thinking" than "Jira configuration mechanics." Different mental muscle entirely.
Focus areas: organizational structure design, product access provisioning, billing management, security policy enforcement, and user lifecycle management. The primary certification is ACP-520 (Atlassian Cloud Organization Admin Certification). If you've ever had to explain to finance exactly why the monthly bill suddenly jumped, or justify to security leadership why MFA isn't uniformly enforced everywhere, or tell a business unit they can't just casually invite anyone with a random Gmail address.. wait, let me finish.. you'll immediately recognize these job responsibilities.
The unique differentiator is operational scope. This path concentrates on organization-level controls rather than individual product configuration details, so you're constantly thinking in terms of access policies, managed account structures, SSO integration, lifecycle automation, and establishing guardrails across Jira, Confluence, and whatever additional tools exist in your Atlassian ecosystem. Career progression typically flows from product admin to enterprise cloud architect, and honestly it can also bridge into broader IAM or SaaS governance positions if you're drawn toward that professional world.
Cloud vs Data Center/Server path decision factors
First consideration is your actual deployment model today. Second consideration is realistic migration timelines. If your company's really moving to Cloud within 12 months, exclusively pursuing Data Center badges might still provide immediate value right now, but it's probably not your smartest long-term investment unless you're specifically supporting that Data Center environment throughout the messy transition period and need credibility while infrastructure's unstable.
Market trends really matter here. Cloud adoption continues climbing steadily, and Atlassian's cloud-first strategic direction is absolutely real, which directly affects the long-term market viability of certain Server/DC-focused certifications over time, even though they remain really valuable in enterprises that can't migrate quickly due to regulatory constraints, complex integrations, or restrictive change control processes.
Skill transferability is decent but definitely not perfect. Permission logic fundamentals, workflow thinking patterns, and scheme hygiene principles carry over nicely. What fundamentally differs is what you can actually configure, what Atlassian manages for you automatically, and how identity provisioning, security policy enforcement, and access management behaves in Cloud environments.
Consultants should think strategically here. Broader market opportunities typically emerge from Cloud credentials combined with at least one deep admin certification, because clients want consultants who can discuss governance strategy and also fix their broken production configuration without constantly escalating to "someone else more qualified."
Multi-certification strategies: building full expertise
If you want maximum career impact, strategically pair certifications that reflect how work actually flows between organizational teams. My favorite combination is a platform cert plus a project-focused cert, because it demonstrates you can handle system-wide governance guardrails and simultaneously help delivery teams ship effectively without constant friction or blockers.
Sequencing really matters. Complete whichever one aligns closest to your current daily work first, then systematically expand outward. A common progression sequence is project admin first, then Jira admin, then org admin if you're transitioning into enterprise-level responsibilities. Time investment is legitimately real. Plan somewhere between 6 to 18 months for completing a full certification path if you're working full-time, because hands-on practice is what actually makes exam content stick in your brain, and also because certification burnout is absolutely a real thing that happens.
Specialized vs generalist approaches
Deep expertise concentrated in one specific area is fantastic if your organization is large and role boundaries are strictly defined. Broad coverage wins in smaller companies where you're literally the "Atlassian person" and you touch absolutely everything from board configurations to billing reconciliation.
Regulated industries often push you toward the org admin and security domains earlier in your career. SMBs typically push you toward project administration first because visible value delivery happens fast. Consulting rewards generalists initially, then gradually pushes you toward developing a specialty once you figure out what clients consistently keep paying you for.
Also, yeah, people definitely care about Atlassian certification salary impact. It varies wildly by geographic region and seniority level, but the more important story is Atlassian certification career impact: you successfully get past HR automated filters, you earn stakeholder trust sooner, and you can legitimately justify higher billing rates when you're consulting.
Atlassian exam difficulty ranking (what to expect)
Atlassian exam difficulty ranking depends more heavily on hands-on practical time than pure study time. Cloud exams can feel "easier" on infrastructure topics but substantially harder on platform governance concepts if you've never actually worked with organization-level controls. Admin exams generally feel harder than project exams because the scope is considerably larger and the potential consequences are significantly bigger.
Which Atlassian certification exam is the hardest? For most people, honestly, it's whichever one sits farthest from their current job responsibilities. A project admin who's never touched global permission schemes will absolutely struggle with ACP-100. A Jira admin who's never managed org-level policies will find ACP-520 feels weirdly abstract and disconnected.
Study resources for Atlassian certification exams
Best study resources for Atlassian certification exams are honestly boring. Official documentation. Atlassian-provided learning paths. A personal sandbox instance where you can safely break things without consequences. Add dedicated hands-on labs around permissions, scheme configurations, workflow design, and automation rules, because passively reading about these concepts absolutely doesn't build the practical instinct you desperately need when exam questions are scenario-based and the clock's aggressively ticking.
Use practice tests carefully and strategically. They're really valuable for pacing practice and identifying weak knowledge spots, not for mindless memorization.
FAQs about Atlassian certification exams
Which Atlassian certification should I take first? Pick whichever one legitimately matches what you're doing weekly, not whichever one sounds most prestigious or impressive.
Are Atlassian certifications worth it for career growth and salary? If your professional work regularly touches Atlassian tools, absolutely yes, because it clearly signals you can operate with substantially less supervision and it directly supports promotion conversations, consulting rate negotiations, and credibility during cross-team change discussions.
Retake policies and exam logistics change periodically, so carefully check Atlassian's current official policies before you schedule anything. Don't casually wing exam-day technical setup. Tiny mistakes create disproportionately big stress.
Atlassian Certification Exams List: Full ACP Exam Breakdown
Atlassian Certification Exams List: Full ACP Exam Breakdown
Look, if you're trying to figure out which Atlassian certification to pursue, you need to understand the complete space first. The ACP (Atlassian Certified Professional) system isn't just random exam codes. There's actual logic to how these certifications break down by deployment model, role, and technical depth.
Understanding the ACP exam naming system
Exam codes reveal more than you'd expect. ACP-100 and ACP-120? Those're system admin certifications. ACP-600 and ACP-620 focus on project-level work. The difference between numbers ending in 00 versus 20 usually indicates deployment model (Data Center/Server versus Cloud), though honestly, that pattern isn't always consistent. It's what I've noticed after working with these exams for a while now.
Here's what matters: Cloud certifications're becoming way more relevant as companies migrate away from self-hosted instances. I mean, the market's shifting hard toward Cloud, so certifications like ACP-120 and ACP-620 are getting more attention from hiring managers who need people familiar with Cloud-specific limitations and capabilities that just don't exist in the on-prem world.
ACP-100: the detailed system admin certification
The ACP-100 is what you take when you're managing Jira Data Center or Server deployments. We're talking 75 questions over 180 minutes, which sounds generous until you hit those scenario-based questions that require you to mentally walk through permission scheme inheritance and workflow post-functions without second-guessing yourself.
This exam covers user management. Permission schemes. Notification schemes. Workflows. All the foundational stuff, but it also goes deep into custom fields, screen schemes, issue security levels, and project roles that interact in ways that'll mess up your entire instance if you configure them wrong.
Advanced topics include global settings configuration, application links between Atlassian products, SSL setup for secure connections. Performance troubleshooting is huge here. Log analysis, JVM tuning, database optimization. Honestly, if you haven't spent time in Catalina logs or adjusted heap sizes on a live system, you'll struggle with those questions that assume you've dealt with real production fires before.
They recommend 6-12 months of hands-on experience before attempting this. That's not just marketing fluff. It's real. You need actual exposure to permissions hierarchy problems, scheme relationship headaches, and workflow post-function debugging. The exam operates at intermediate to advanced difficulty, and the passing score requirements reflect that depth they're testing for.
Career-wise, this certification's necessary if you're pursuing Data Center or Server administrator roles. Companies still running on-premises deployments need admins who can handle system-wide configuration and maintenance without breaking production environments during peak business hours.
Study timeline? 4-8 weeks for experienced administrators who already know their way around system configuration but need to fill knowledge gaps and practice scenario analysis. I once spent six weeks preparing for this while also migrating a 500-user instance to new hardware, which was probably not the smartest timing, but deadlines don't care about your study schedule.
ACP-120: Cloud-native system administration
The ACP-120 targets administrators managing Jira Cloud instances exclusively. Same format as ACP-100 (75 questions, 180 minutes) but the content diverges significantly because Cloud has different capabilities and limitations that'll catch Server admins off guard.
Cloud user management works differently. You're dealing with organization structure, site administration through a web UI, and Cloud-specific security controls instead of direct server access. No direct database access. No JVM tuning to optimize performance. No custom database queries to fix data issues that users created.
Instead, you focus on automation rules. The Cloud automation builder is powerful but different from Server plugins. Cloud apps from the marketplace, API management for integrations with external systems. Atlassian Access integration for SSO and advanced security features. Understanding what you cannot configure in Cloud versus what you could do in Data Center? That's critical exam knowledge they test repeatedly.
The Cloud UI simplifies some things but restricts others in frustrating ways. You need hands-on experience with the organization admin console, Cloud-specific workflows, and Cloud automation capabilities that don't match Server functionality. Market relevance's increasing rapidly. Not gonna lie, more job postings ask for Cloud experience now than Server/Data Center combined in most markets.
Study focus should emphasize Cloud automation. Organization-level administration. Cloud-specific workflow limitations. 3-6 weeks preparation time if you already have Cloud experience. Longer if you're transitioning from Server/Data Center background without touching Cloud before.
ACP-600: project-level configuration for Server/Data Center
ACP-600 is different. It's for project administrators, team leads, project managers. People who configure projects but don't have system-wide admin access to mess things up. 60 questions in 90 minutes. Faster pace, more practical scenarios you'd encounter daily.
You're setting up projects. Configuring boards. Customizing workflows at the project level without system admin help. Creating filters that actually make sense. Heavy Agile focus here: Scrum and Kanban board setup, sprint management, backlog refinement for teams that actually ship code regularly.
Reporting and dashboards through gadget configuration, JQL for filtering and reporting, custom filter creation that doesn't break when someone renames a field. Team collaboration features matter here: notifications, watchers, project permissions, issue type schemes that don't confuse new users completely.
You need 3-6 months project administration experience realistically. The skills tested're practical project setup and team support capabilities, not deep technical system configuration that breaks production environments.
This certification's ideal for non-technical administrators. Team coordinators. People who need to prove they can set up and maintain project environments without constantly escalating to system admins for basic configuration tasks.
Study focus: JQL mastery is huge here. Board configuration options that teams actually use. Workflow basics without getting into post-functions and validators. 2-4 weeks preparation for experienced project admins who already do this work daily.
ACP-610: advanced project management for on-premises
ACP-610 takes project administration to the next level for Data Center and Server deployments where things get complicated fast. This's for senior project administrators and technical project managers who handle complex multi-project environments with dependencies everywhere.
You're dealing with complex workflows. Automation at the project level. Advanced JQL queries that'd make beginners cry. Project hierarchies, shared configurations across multiple projects, project templates that actually work when you deploy them.
Cross-project reporting that makes sense. Project dependencies. Linked issues across project boundaries without creating circular reference nightmares. Performance considerations become relevant here: project-level optimization, best practices for large projects with thousands of issues that don't load slowly.
You need significant hands-on experience managing multiple complex projects before attempting this exam, because they assume you've already dealt with these problems in production. Career relevance? Positions requiring deep project-level technical expertise. Companies with mature Jira deployments and complex project structures need people who can optimize and maintain these environments without guidance.
4-6 weeks preparation with advanced experience. Less if you're already troubleshooting complex workflow issues and building advanced automation rules regularly without breaking things.
ACP-620: Cloud project management specialization
The Cloud version ACP-620 focuses exclusively on project administration in Jira Cloud environments where the rules're different. Cloud automation builder's central here. It's more accessible than Server plugins but has different capabilities that limit what's possible.
Cloud-specific board features. Simplified configurations compared to Server/Data Center. Cloud-native integrations that actually work without custom development. You're working with marketplace apps designed for Cloud, managing external user access, setting up Cloud-specific sharing and collaboration features that don't exist in Server.
The differences from ACP-610 reflect Cloud limitations and Cloud-native capabilities they've built specifically for this model. Some advanced Server features don't exist in Cloud at all. Some Cloud features don't exist in Server. You need to know both what's possible and what's not, which honestly confuses people transitioning between platforms constantly.
Growing demand as Cloud adoption accelerates industry-wide. 3-5 weeks preparation with Cloud project experience. The Cloud automation builder requires hands-on practice. You can't just read about it and expect to answer scenario questions correctly when they throw edge cases at you.
ACP-520: organization Cloud governance
ACP-520 operates at the organization level. This's for organization administrators, IT managers, architects managing Atlassian Cloud at scale across entire companies with hundreds of users.
Organization structure. Product access management across teams. User provisioning across multiple Cloud products without creating security holes. Security and compliance through Atlassian Access: SSO, SAML configuration, audit logs, data residency requirements that legal departments care about.
Managing multiple Cloud products (Jira, Confluence, Bitbucket) from the organization console without losing your mind. Billing and licensing management, subscription optimization, user licensing strategies, cost control that CFOs actually notice.
User lifecycle management at scale. Onboarding processes, offboarding procedures, access reviews, group management across products that don't create orphaned accounts. API usage at the organization level, bulk operations, scripting for automation that saves hours weekly.
You need experience managing Atlassian Cloud at the organization level, not just individual sites that five people use. Skills tested include governance practices, security controls, cross-product administration that actually matters at scale.
Career relevance's critical for Cloud administrator and architect roles at larger companies. Companies moving to Cloud need people who understand organization-wide governance and security frameworks. 4-6 weeks preparation for administrators already working at this level daily.
Choosing your certification path
Which exam should you take first? Depends entirely on your role and deployment model you're working with. If you're managing Cloud instances, start with ACP-120 for admin work or ACP-620 for project focus. If you're working with Data Center or Server, ACP-100 or ACP-600 depending on your responsibilities and what your boss actually needs.
The difficulty ranking generally goes: ACP-600 (easiest, project-level focus), then ACP-620/ACP-610 (intermediate, advanced project work), then ACP-120/ACP-100 (harder, system-wide administration), then ACP-520 (organization-level complexity). But honestly, difficulty depends heavily on your actual hands-on experience with the specific deployment model and scope they're testing, not just what the exam blueprint says about complexity levels.
Don't chase certifications without the underlying experience backing them up. These exams test practical knowledge, not memorized facts from documentation. Get the hands-on work first, then validate it with certification when you're actually ready.
Atlassian Exam Difficulty Ranking: Strategic Exam Selection
Atlassian certification exams: overview
Atlassian certification exams? They're honestly this strange combo of hands-on admin stuff and obscure trivia you'd only figure out after something explodes right before a weekend. They prove you can really run Jira and its siblings, not just fumble around hoping error messages vanish.
What they actually measure shifts by track. Some focus on project-level work, where you're deep in workflows, issue types, and permissions for specific teams. Others cover system-wide territory, where you're managing how the entire instance functions, identity handling, protective guardrails, and what goes wrong when projects start interfering with each other. Then there's organizational admin space, which isn't about "build a workflow" but more like "prevent an enterprise from self-destructing through chaotic access patterns."
Atlassian certification paths typically divide between Cloud and Data Center/Server. That's where the Jira Cloud vs Data Center certification debate gets interesting. I mean, Cloud strips away configuration options but introduces platform-wide governance quirks and limitations, whereas Data Center/Server provides endless dials and assumes you understand what breaking each one actually causes.
Admins, project admins, and org admins all gain value, just differently. If you're transitioning into a Jira administrator certification position, these credentials help you clear the "we need proven expertise" hurdle. For consultants, you'll notice Atlassian certification career impact matters because clients appreciate visible credentials, honestly even when your real worth is staying composed during crisis troubleshooting.
Atlassian certification paths (role-based)
Jira administrator path (admin-focused)
This represents the "control the system" track. You've gotta grasp global permissions, authentication frameworks, directory and group architecture, schemes affecting numerous projects, and how modifications cascade through everything. More structural thinking, less "just my team's needs."
Also more accountability. Won't sugarcoat that.
Jira project administration path (project-focused)
Project-level configuration might seem smaller in scale, but it's not inherently simpler. You still must comprehend how workflows, screens, fields, permissions, and notifications interconnect, and exams absolutely hammer those relationships since that's precisely where people screw up in actual environments.
Atlassian Cloud organization admin path (org-wide governance)
Governance sits here. User provisioning, app oversight, security frameworks, and how multiple products operate under unified org structure. The technical work feels different, and the "challenge" stems from coverage breadth and policy reasoning, not memorizing button locations in workflow designers.
Atlassian ACP exams list (ACP exams)
Here's the Atlassian ACP exams list we're ranking, with the ones you should legitimately integrate into your preparation strategy.
ACP-100: Jira Administrator Exam
Targeting full admin expertise on Server/Data Center? Start here: ACP-100 Jira Administrator Exam.
ACP-600: Project Administration in Jira Server
Project admin foundations for Server: ACP-600 Project Administration in Jira Server.
ACP-520: Atlassian Cloud Organization Admin Certification
Org-level governance in Cloud: ACP-520 Atlassian Cloud Organization Admin.
ACP-120: Jira Administration for Cloud
System-wide Cloud admin: ACP-120 Jira Administration for Cloud.
ACP-620: Managing Jira Projects for Cloud exam
Project admin in Cloud: ACP-620 Managing Jira Projects for Cloud.
ACP-610: Managing Jira Projects for Data Center and Server certification
Project admin, broader flexibility: ACP-610 Managing Jira Projects for Data Center and Server.
Atlassian exam difficulty ranking (what to expect)
Difficulty across Atlassian certification exams isn't singular. It's layered dimensions that accumulate: technical depth (do you merely recognize the interface, or really understand underlying systems), scope breadth (single project versus entire installation), and practical requirements (have you legitimately performed this work, or just skimmed documentation once).
Personal background influences outcomes more than anyone acknowledges. Someone from service management backgrounds might find workflows and SLAs natural but struggle with permission schemes and group architecture. Another person might excel at directory and SSO configuration yet get demolished by Jira scheme interactions because they've never diagnosed why one project's issue type screen lacks fields while another displays everything. Same certification. Different suffering.
I once watched a consultant with eight years of Confluence experience completely bomb a basic Jira workflow question because he'd never actually built one from scratch. Experience matters, but only the right kind of experience.
Technical complexity factors that influence exam difficulty
Depth counts significantly. Surface knowledge is "I can build a workflow." Architectural comprehension is "I understand what occurs when workflow schemes are shared, when projects use common field configurations, and when permission modifications affect browse capabilities across multiple teams." The exams, particularly admin-focused ones, reward that second understanding.
Interconnected concepts matter enormously. Schemes, workflows, permissions, notifications, fields, screens. Their interdependencies. One adjustment can fracture three configurations, and exam questions frequently resemble actual support tickets you'd receive. The thing is, the answer isn't a feature label but a diagnosis of what's connected beneath the interface.
Troubleshooting represents the hidden cost. Some questions ask "what setting controls X." Others present "user can't perform Y, what's the probable cause." That demands diagnostic capability, not pure configuration memorization.
Advanced feature coverage adds substantial weight. Automation rules, scripting concepts (even without writing code, you must think like rule engines), API integration fundamentals, app behaviors, and custom development boundaries. Cloud introduces its unique complications here because you must know what's impossible, which sounds straightforward until exam pressure makes two answers appear equally valid.
Scope and breadth considerations
System-wide administration spans wider than project-level setup. Project-level gets complicated rapidly though when you're reasoning about schemes shared across dozens of projects, or when questions imply constraints you'd only encounter in mature instances.
Single-product concentration versus multi-product org management transforms everything. Jira-only questions feel contained. Org admin questions might touch identity, access policies, app governance, security frameworks, and cross-product configurations.
Cloud simplicity versus Data Center/Server flexibility is legitimate. Cloud eliminates certain "deep configuration" zones, yet forces you to comprehend Cloud-specific boundaries, what Atlassian manages, and what compensating controls exist when you can't modify server settings.
Hands-on experience requirements
Minimum experience isn't merely suggested. If you haven't invested time working through permission schemes, testing with varied user accounts, deliberately breaking a workflow, and repairing it, you'll feel like exam language is slightly foreign.
Practical exposure crushes theoretical study. Documentation helps obviously, but hands-on practice teaches the mental framework, and that framework is what you apply when scenario-based questions describe symptoms instead of naming the configuration setting.
Real-world scenario complexity explains why these exams feel "difficult." The strongest questions resemble Slack messages: "Hey, why can't contractors transition issues in Project X but they manage fine in Project Y." That's not memorization. That's accumulated experience.
Suggested difficulty ranking from beginner to advanced
This is my Atlassian exam difficulty ranking, and yeah, it's subjective because your background completely reshapes everything.
Entry level: ACP-600 (Project Administration in Jira Server). Concentrated scope, practical application, and it establishes core Jira mechanics without forcing enterprise governance reasoning.
Entry-intermediate: ACP-620 (Managing Jira Projects for Cloud). Cloud's interface and protective boundaries can minimize chaos, though you still need solid scheme and workflow understanding.
Intermediate: ACP-610 (Managing Jira Projects for Data Center and Server). Broader than ACP-600, more configuration options, more "which approach is optimal" question styles.
Intermediate-advanced: ACP-120 (Jira Administration for Cloud). System-wide focus, and Cloud constraints mean you must know product limitations and proper admin patterns cold.
Advanced: ACP-100 (Jira Administrator Exam). This is the ACP-100 Jira Administrator Exam for legitimate reasons: deep coverage, wide scope, and it expects architecture-level consequence understanding.
Advanced-specialized: ACP-520 (Atlassian Cloud Organization Admin). The ACP-520 Atlassian Cloud Organization Admin exam is less about Jira screens and more about governing enterprise organizations, and that's a distinct type of challenge.
How deployment model affects difficulty perception
Cloud certifications often present narrower scope, but they require understanding Cloud-specific limitations and the "correct approach" when you can't customize everything. Data Center/Server certifications offer broader coverage, deeper technical complexity, and more opportunities for tricky "gotchas" around shared configurations and instance-wide consequences.
Cloud exams aren't automatically simpler. Look, simplified interfaces can mask complexity, and exams still probe what happens when you combine product access, project permissions, and org policies. Plus you need to know what's impossible in Cloud so you don't select answers that sound like traditional Server behavior.
Experience level recommendations for each certification
Beginner, 0-6 months: begin with project administration certifications like ACP-600 or ACP-620. Learn how Jira components connect. Break configurations safely. Repair them.
Intermediate, 6-18 months: advance to system administration like ACP-120 or ACP-100 depending on Cloud vs Server/DC emphasis. This is where you transition from "my project" thinking to "my platform" ownership.
Advanced, 18+ months: pursue org-level or specialized credentials like ACP-520, particularly if you're handling enterprise governance, multiple products, and security frameworks.
Consultant perspective: a multi-certification approach makes sense when your client portfolio is varied, because one engagement you're configuring Jira Software projects, and the next you're resolving org access issues, app proliferation, and policy decisions affecting every team and every billable hour.
Common difficulty misconceptions and realities
Fewer questions doesn't mean easier examination. Intensity matters significantly. A brief exam can still be punishing if every question is scenario-driven and every answer is "technically accurate" but only one represents the optimal admin decision.
Cloud vs Server difficulty represents a flawed comparison. Different challenges entirely. Server/DC demands knowing more configuration options. Cloud requires thinking within constraints and knowing boundaries precisely.
Project admin vs system admin is a scope transition, not a simple difficulty progression. Some people find system admin easier because it's more structured. Others find project admin harder because it's closer to messy team dynamics and unconventional workflows.
Choosing the right exam based on your experience level
Self-assessment comes first. Be brutally honest about hands-on time. If you've never tested permission modifications with multiple user types, you're unprepared for exams assuming you can debug access problems from symptoms alone.
Job role alignment matters substantially. If your current or target position is project admin, don't rush into ACP-100 just because it sounds impressive. Select the certification matching what you actually do, then expand outward.
Learning curve and time constraints are legitimate factors. If you've only got six weeks and limited lab access, choose an exam with tighter scope and heavier overlap with your daily work, because "study time" without practice is how people burn out spectacularly.
Strategic sequencing for building expertise
Foundation first works best. Start project-level, then progress to system-level, because project configuration forces you to learn the fundamental building blocks that system administration depends upon.
Deployment model consistency helps tremendously. Complete a Cloud track before switching to Data Center, or vice versa, because mixing mental models prematurely leads to careless mistakes, like selecting a Server-style answer for a Cloud limitation question.
Easier exams prepare you for challenging ones by teaching relationships. That's the entire point. The difficult part of Jira isn't creating workflows. It's understanding what else you just modified.
Factors that can make any exam more challenging
Limited hands-on access to test environments will hurt you. Experience gaps with automation, scripting concepts, or integrations make certain questions feel like they're written in a different language. Weak comprehension of scheme relationships matters more than people realize. Permissions, workflows, screens. Poor preparation strategy, especially depending solely on dumps instead of genuine Atlassian certification study resources and lab practice, is the classic mistake. One of these might hurt you. Two will absolutely sink you.
How to assess exam difficulty for your specific situation
Review official objectives and map them to tasks you've legitimately performed, not tasks you've merely read about. Evaluate your experience honestly against required capabilities. Ask others who completed the exam what surprised them, but filter for background similarity because a Cloud-first admin and a Server veteran will complain about completely different aspects.
Practice tests help if you use them correctly. Not as memorization exercises, but as gap detectors, where every incorrect answer becomes a lab task you reproduce and resolve.
And yeah, the career angle is legitimate. Atlassian certification salary increases occur more frequently in consulting and platform ownership positions, and the Atlassian certification career impact is strongest when the credential matches work you're already performing or work you're actively transitioning into.
faqs about Atlassian certification exams
Which Atlassian certification should I take first? Begin with project administration, typically ACP-600 for Server/DC exposure or ACP-620 for Cloud, unless your role is already system admin work.
What is the difference between ACP-100 and ACP-120? ACP-100 targets Server/Data Center depth and flexibility, while ACP-120 targets Cloud system administration with Cloud limitations and Cloud admin patterns.
Are Atlassian certifications worth it for career growth and salary? Frequently yes, especially when combined with genuine admin experience and when you're targeting roles that own Jira or govern an Atlassian organization.
Which Atlassian certification exam is the hardest? For most candidates, ACP-100 or ACP-520, depending on whether deep Jira architecture or enterprise Cloud governance feels more unfamiliar.
What are the best study resources for Atlassian certification exams? Official objectives and documentation, hands-on labs in sandbox environments, and scenario-style practice questions that force you to diagnose root causes, not just recognize terminology.
Career Impact of Atlassian Certifications: Professional Growth Opportunities
How Atlassian certifications actually change your career trajectory
These credentials really matter. I've watched people jump from basic support roles to leading enterprise implementations just because they got certified. These aren't participation trophies. Atlassian certifications fundamentally shift how organizations see you and, honestly, what opportunities land in your inbox.
The job market data? Pretty clear story there. In 2026, postings requiring Atlassian certifications are up about 40% compared to three years ago. Not just "nice to have" mentions either, but hard requirements. Companies hiring for Jira Administrator roles now explicitly ask for ACP-100 or ACP-120 depending on whether they're running Data Center or Cloud. Same pattern with project-level roles asking for the ACP-620 or ACP-610 certifications right in the job description.
What's interesting? How these credentials function as filters. I mean, you might have five years of hands-on Jira experience, but if the recruiter's scanning for specific cert codes, your resume might not even make it to a human. The certification becomes this shorthand that gets you past both automated systems and initial screening rounds.
Specific roles these certifications unlock
Jira Administrator positions? Most obvious win. With something like the ACP-100, you're qualified to handle system-wide configuration across an entire organization. We're talking global permission schemes, custom field management, workflow design that affects hundreds of projects. Companies with 500+ users absolutely need someone who can prove they understand the architecture at that scale.
Jira Project Administrators work at a different level. More team-focused, less architectural. The ACP-610 or ACP-620 certifications show you can support individual teams without breaking stuff for everyone else. This role gets overlooked, but it's perfect if you're transitioning from a project management background and want to add technical depth.
Then there's the Atlassian Cloud Organization Administrator role, which didn't really exist until recently. The ACP-520 certification covers enterprise governance, security policies, user provisioning across products. If your company's moving to Cloud or already there, this certification makes you the obvious choice to own that environment.
Atlassian Consultant positions become realistic once you're certified. Clients want to see credentials. Period. They're paying $150-200/hour for your advice, so they need that third-party validation that you actually know what you're doing. I've seen consultants struggle to close deals without certs even when they had better practical experience than certified competitors.
Solution Architect roles at the enterprise level? Almost always require certification now, plus usually multiple years of implementation experience. You're designing systems that might serve 10,000 users across dozens of business units. Nobody's trusting that to someone who can't prove baseline competency. (Side note: I once worked with an architect who had zero certs but ten years experience, and he spent half his client meetings defending his expertise instead of actually solving problems. Eventually he just got certified to stop the questions.)
DevOps Engineers with Atlassian certifications stand out because they understand both the tools and the workflows. You can integrate Jira with Jenkins, GitHub, whatever, but more importantly you understand how teams actually use these integrations. That workflow knowledge separates decent DevOps folks from great ones.
How certifications affect your internal career mobility
Getting promoted? Not just about doing good work. It's about proving you're ready for the next level, and when you earn an Atlassian certification, you're sending a signal to management that you're serious about professional development. Not gonna lie, this matters more than it probably should. Managers notice when someone invests their own time in getting certified.
I've watched this play out during salary review cycles. Two people doing similar work, but one has certifications, and guess who has more ammunition when negotiating? The certified person can point to validated skills, not just "I think I'm good at this."
You also become more visible. Once you're certified, suddenly you're the one other teams ping when they have questions. That cross-team visibility? Huge for moving into leadership positions. You're not just the admin for your department anymore. You're the subject matter expert for the whole company.
Leadership roles like team lead, manager, director positions increasingly expect technical credentials to back up practical experience, so when you're competing for a promotion against three other qualified people, certification can be the tiebreaker. I mean, it's concrete proof you can do the work, which makes it easier for leadership to justify promoting you.
Internal consulting opportunities open up too. Maybe you start supporting multiple teams or departments instead of just one, or your company might create a Center of Excellence around Atlassian tools and put you in charge. These hybrid roles that blend technical knowledge with advisory work almost always go to certified folks because they have credibility across the organization.
Building credibility with stakeholders who control your career
Here's something nobody talks about enough. Certification changes how people listen to you in meetings. When you propose changing a workflow or implementing automation, stakeholders take you more seriously if they know you're certified. It's like having credentials on your email signature that say "I actually know what I'm talking about here."
Management confidence? Goes up dramatically. If you're suggesting a major change like migrating from Server to Cloud, executives want assurance you understand the implications, and certification provides that assurance without them needing to evaluate your skills themselves.
Training others becomes easier when you're certified because people trust your knowledge more readily, whether you're running formal training sessions or just helping colleagues. That certification badge carries weight. New hires especially respond better when they know they're learning from someone with validated know-how.
Executive leadership pays attention differently when you're driving strategic initiatives. If you're proposing a multi-year Atlassian roadmap or major architectural changes, being certified makes those conversations smoother. You're not just some IT person with opinions. You're a certified professional making data-driven recommendations.
The vendor relationship advantages? Real. Atlassian and their partner network recognize certified professionals, so you might get early access to beta programs, invitations to special events, or connection to resources not available to uncertified users. These relationships can accelerate your career in unexpected ways.
Real-world skills that employers actually pay for
Governance know-how is probably the most undervalued skill out there. Understanding permissions, security models, compliance requirements, audit capabilities, this stuff matters enormously in regulated industries or large enterprises. The ACP-520 really digs into this, and companies desperately need people who can handle it properly.
Workflow design and optimization directly impacts productivity. If you can automate business processes and eliminate manual work, you're making the company money. Employers value this because it's measurable. You can point to hours saved or errors reduced.
Integration capabilities matter more every year as tool ecosystems get more complex. Can you connect Jira to Salesforce? Confluence to Slack? ServiceNow to Jira Service Management? These integrations are what make Atlassian tools powerful, and certified people understand how to implement them without creating maintenance nightmares.
Automation skills using Jira Automation rules or ScriptRunner reduce operational overhead. I've seen single automation rules save teams 10+ hours per week. That's real value that shows up in team velocity and capacity planning.
Troubleshooting proficiency becomes critical when something breaks and 500 people can't work. Certified administrators can diagnose complex issues quickly based on understanding the underlying architecture, not just surface-level symptoms.
Migration know-how, whether Cloud migrations, instance consolidations, or platform upgrades, is incredibly valuable right now. Companies are paying premium rates for people who can execute these transitions without data loss or extended downtime.
Different organizational contexts where certification adds value
Enterprise environments with thousands of users? Need certified administrators because the complexity is just too high otherwise. You're managing dozens of projects, hundreds of workflows, complex permission schemes. Certification proves you can operate at that scale.
Small to medium businesses often hire one person to handle multiple roles, so if you're certified across several Atlassian products, you become that Swiss Army knife employee who can support the whole stack.
Consulting firms absolutely require certification for client-facing roles. Table stakes. You're representing the firm's know-how, and clients expect credentials.
Managed service providers supporting multiple client instances need certified staff to deliver consistent quality across different environments and use cases.
Consulting and freelance opportunities
Independent consulting becomes viable once you're certified. Why? Because you can point potential clients to verified credentials, and nobody's hiring an uncertified freelancer for serious money when certified options exist.
Hourly rate premiums for certified consultants run 20-40% higher than non-certified folks with similar experience. That certification literally translates to higher income per hour worked. Over a year, that adds up to real money that justifies the exam cost many times over.
Conclusion
Look, getting certified in Atlassian tools isn't just about passing an exam. It's about proving you actually know what you're doing when someone's Jira instance goes sideways at 3pm on a Friday. I've seen plenty of people wing these tests and fail spectacularly.
The thing is, whether you're going after the ACP-100 for general Jira administration or diving into something more specific like the ACP-520 for cloud organization management, you need real preparation. Not gonna lie, these exams test practical knowledge that you'll actually use. The ACP-600 and ACP-610 both cover project administration but for different deployment types, and yeah that matters more than you'd think when you're troubleshooting workflow issues.
Here's what I tell people.
Practice exams? Your best friend. You can read documentation until your eyes bleed, but nothing simulates the actual test like working through realistic questions under time pressure. I mean, honestly, the real value isn't just memorizing answers but understanding why certain configurations work and others create absolute chaos in production. Everyone's pinging you at once asking what happened.
If you're serious about prepping, check out the practice resources at /vendor/atlassian/ where you'll find materials for all the major certs. They've got specific prep for everything from the ACP-120 cloud administration exam to the ACP-620 and ACP-610 project management certifications. Working through those practice questions will expose gaps in your knowledge you didn't even know existed. Like, I thought I had permissions down cold until a practice scenario completely stumped me.
The certification space for Atlassian keeps shifting as they push more features into Cloud versus keeping Data Center relevant for enterprise clients. You need to stay sharp. It's kinda frustrating sometimes because what you learned six months ago might've changed, but that's just how it goes with these platforms. My cousin works at a consulting firm and he's constantly complaining about having to relearn the new permission schemes every quarter. Gets old fast.
Don't just study the night before and hope for the best. Give yourself three weeks minimum. Work through practice exams multiple times. Actually lab out the scenarios in a test instance if you can. I know not everyone has access, but it makes a difference. These certifications open doors to better roles and higher pay, but only if you actually earn them properly. The people hiring you will know within one conversation whether you crammed or really understand the platform.
Get your prep materials lined up.
Block out study time. Go pass that exam.
