Introduction-to-Cryptography Exam Guide
Introduction-to-Cryptography is best approached as a fundamentals assessment: you should be able to explain why cryptography is used, distinguish major cryptographic methods, and select the right purpose for encryption, hashing, signatures, and certificates. The available catalogue context does not publish an official blueprint, score, question count, time limit, prerequisite, language, or delivery method. This guide therefore helps you decide what to study first, how deeply to study each topic, and which exam details must be confirmed before scheduling.
What should this exam prepare you to explain?
Start with purpose and relationships, not algorithm names. A candidate working at an introductory level should be ready to explain how cryptography protects information, how plaintext becomes ciphertext, why keys matter, and how different cryptographic functions address confidentiality, integrity, authentication, or non-repudiation.
The official material supplied for this guide does not identify an exam owner or publish a formal competency blueprint for Introduction-to-Cryptography. It does, however, provide a consistent foundation for study. Microsoft Learn frames cryptography around confidentiality, integrity, and availability and lists basic concepts, encryption, hashing, digital signing, and digital certificates as learning objectives. AWS identifies confidentiality, integrity, authentication, and non-repudiation as primary cryptographic goals. EC-Council’s beginner course adds symmetric-key cryptography, public-key cryptography, AES, RSA, Diffie-Hellman, elliptic-curve cryptography, hashing, and digital signatures.
Treat those subjects as an evidence-based preparation scope rather than as a guaranteed list of exam domains. Until the exam owner publishes an outline, do not assign official weights, assume a particular algorithm will appear, or infer that a training module’s assessment is the same examination as the catalogue item.
A useful readiness test is whether you can answer three questions for any cryptographic mechanism: what security property does it support, what inputs or keys does it use, and what problem does it solve in a real communication or storage scenario? If your answer is only a definition, your preparation is not yet practical enough.
Who is the likely audience?
The source material is explicitly accessible to beginners and includes business-owner, business-user, and student audiences in the Microsoft Learn module. That makes this exam title more suitable for candidates establishing security vocabulary than for candidates seeking an advanced cryptographic engineering assessment. Learners may include aspiring security professionals, administrators, developers, cloud practitioners, and nontechnical staff who need to understand security controls.
Your starting point should depend on your current knowledge. A newcomer should first learn the security goals and basic terminology. Someone with infrastructure or application experience can move sooner to key use, certificate purpose, and the distinction between encryption, hashing, and signing. An experienced security practitioner should still verify the introductory scope rather than assume that familiarity with tools equals mastery of cryptographic concepts.
What is not confirmed?
No supplied source confirms the exam provider, official prerequisites, registration process, delivery platform, exam fee, duration, number of questions, question types, passing score, retake policy, available languages, or current status. These are scheduling facts, not details to estimate from unrelated training pages.
Before paying or booking, locate the official exam page associated with the catalogue identifier and verify each item directly. If the official page does not publish a detail, treat it as unknown. Do not substitute the Microsoft module assessment, the EC-Council course, or a third-party practice product for confirmation of the Introduction-to-Cryptography examination.
Which concepts deserve first priority?
Build a four-part mental model: security goals, cryptographic transformations, key relationships, and trust mechanisms. This sequence prevents a common beginner error—memorizing algorithm labels without knowing whether a mechanism protects secrecy, detects alteration, authenticates a sender, or supports a verifiable signature.
Cryptography can protect information at rest, electronic communication, and information in use, according to the supplied Splunk source. AWS describes encryption as converting plaintext into ciphertext with an encryption algorithm and one or more keys. Learn those terms as a process: plaintext is the original information; ciphertext is the transformed representation; encryption and decryption are related operations; and the key controls how the operation is performed.
The four AWS goals provide a useful decision framework. Confidentiality limits disclosure to intended or authorized parties. Integrity concerns whether information has been changed. Authentication helps establish who sent a message or which party is involved. Non-repudiation addresses the ability to support the authenticity of a signature so that the signer cannot credibly deny it. Different tools can contribute to these goals, but the goals are not interchangeable.
Microsoft’s module also places availability within the broader protection role of cryptography. At introductory level, avoid treating availability as something encryption automatically provides. Ask instead how a cryptographic control fits into a wider security design and whether loss, misuse, or unavailability of keys could affect access to protected information.
Make a one-page table with columns for goal, mechanism, key use, and example. Fill it from memory, then correct it using the official sources. This is more useful than copying paragraphs because it forces you to distinguish overlapping terms.
How do encryption and decryption relate?
Encryption changes readable plaintext into ciphertext, while decryption restores the readable information for an authorized recipient. The important study question is not merely whether data is encrypted; it is who can decrypt it, how the key is distributed, and whether the design also needs integrity or sender authentication.
For a simple exercise, describe a message moving between two parties. Identify the plaintext before protection, the ciphertext during transport or storage, the relevant key or keys, and the authorized decryption step. Then ask what would happen if an attacker could alter the ciphertext or impersonate the sender. That final question shows why encryption alone may not address every security goal.
Why is key management part of the subject?
A cryptographic design depends on its keys, so key management is not an administrative footnote. The supplied Splunk material identifies generation, distribution, and rotation as key-management tasks and explains that system security heavily relies on cryptographic keys.
Study key management as a lifecycle rather than a single storage question. Be able to discuss why a key must reach an authorized party, why access should be controlled, why replacement may be needed, and why losing a decryption key can affect access to protected information. Keep the discussion conceptual unless the official exam outline supplies implementation requirements.
Can you distinguish symmetric and asymmetric cryptography?
The distinction is essential: symmetric-key cryptography uses the same key for encryption and decryption, while asymmetric or public-key cryptography uses separate public and private keys. Learn the operational trade-off and the typical purpose of each rather than treating one category as universally better.
AWS describes symmetric cryptography as using the same key for encryption and decryption. Splunk characterizes it as efficient for bulk data. This gives you a practical question to ask in a scenario: if a system must protect a large volume of data efficiently, which family is likely to be relevant, and how will the parties securely obtain or manage the shared key?
AWS describes asymmetric cryptography as using separate public and private keys. Splunk associates public/private key pairs with secure key exchange and digital signatures. The public key can be shared more broadly, while the private key must remain under the control of its owner. Do not describe the pair as two interchangeable passwords; their roles are different.
Hybrid encryption combines the strengths of both families in a broader design. Splunk identifies hybrid encryption as another type used to secure data and communications. At exam-preparation level, understand the rationale: a system may use public-key techniques for an exchange or trust operation and symmetric encryption for efficient data protection. Avoid asserting a particular protocol sequence unless the official exam material specifies one.
Use comparison prompts instead of flashcards that only ask for definitions. For each method, explain key relationship, typical use, primary advantage, and the risk created by poor key handling. Then explain why a system might use both methods rather than choosing only one.
What should you know about AES and RSA?
Know AES as a symmetric block cipher and RSA as an asymmetric encryption algorithm. The goal is to place each in the correct category and explain the kind of problem it addresses; it is not to recite implementation trivia without context.
The supplied Splunk source states that AES block-cipher key sizes can be 128, 192, and 256 bits and that encryption occurs in blocks of 128 bits each. It identifies RSA as an asymmetric encryption algorithm and attributes its invention to Ron Rivest, Adi Shamir, and Leonard Adleman in 1978. These are supported facts worth recording accurately if the exam assesses algorithm recognition.
Do not turn those facts into a claim about which AES option or RSA setting the exam requires. The supplied research does not publish an algorithm-selection policy for this exam, nor does it state that memorizing key sizes is sufficient. Focus on category, purpose, and the relationship between algorithm and key.
Where do Diffie-Hellman and elliptic-curve cryptography fit?
Study Diffie-Hellman and elliptic-curve cryptography as public-key or asymmetric-cryptography topics, while checking the exact treatment in the official exam outline when available. The EC-Council beginner course explicitly includes both, but its course coverage is not proof that the exam uses the same sequence or depth.
For preparation, write a short explanation of the problem each topic is associated with, then compare it with encryption and signatures. Do not collapse key agreement, encryption, and signing into one generic activity. If you cannot state what parties need to possess before communication and what outcome the operation produces, revisit the underlying public/private-key model.
How are hashing, message authentication, and signatures different?
Hashing, message authentication codes, and digital signatures all appear in integrity discussions, but they do different jobs. A hash function produces a digest for comparison; a message authentication code combines a message with a shared secret for integrity and authentication; a digital signature uses asymmetric cryptographic roles to support integrity, authentication, and non-repudiation in an appropriate design.
AWS lists hash algorithms, digital signatures, encryption algorithms, and message authentication codes among cryptographic tools or functions. Microsoft’s learning objectives separately identify hashing and digital signing. Treat the separation as a core study requirement: a digest alone does not prove who created a message, and encryption alone does not automatically create a signature.
Splunk lists SHA-1, SHA-2, SHA-3, MD5, Whirlpool, Blake 2, and Blake 3 among common hashing algorithms. For an introductory exam, learn the idea of a one-way-style digest and the use of hashes in detecting changes, but do not infer that every listed algorithm has the same security standing or current recommended use. The supplied facts do not provide a policy ranking or deprecation schedule.
A strong practice exercise is to take four requirements—hide a document, detect alteration, authenticate a sender, and support a signed statement—and map each to the most relevant mechanism. Then explain what additional key or trust information is needed. This exposes the common mistake of selecting “encryption” for every security requirement.
Avoid saying that a hash “encrypts” data. A digest is not a reversible ciphertext, and the purpose of hashing in the supplied material is tied to integrity and signing applications. Avoid saying that a digital signature is simply an encrypted hash unless the question specifically presents that simplified model and you can preserve the distinction between signing, verification, and encryption.
What does a digital signature establish?
A digital signature is used to support verification of a message’s origin and integrity and to contribute to non-repudiation. Study the roles of the signing key, verification key, signed data, and verification result. The key question is what the recipient can verify, not whether the message was made secret.
Use a document example: a sender signs a message, a recipient verifies the signature with the relevant public information, and a change to the signed content should affect verification. Then ask whether confidentiality was required. If it was, add encryption as a separate requirement rather than assuming the signature hides the content.
When is a message authentication code appropriate?
A message authentication code is a cryptographic function that can help confirm integrity and authenticity for parties sharing the relevant secret. AWS includes message authentication codes among cryptographic tools, but the supplied sources do not specify a particular MAC algorithm or exam scenario.
Prepare by comparing a MAC with a digital signature in terms of key relationship and verification audience. A shared-secret design and a public/private-key design create different trust and distribution questions. Keep your answer conceptual unless the official objectives require named constructions.
Why do digital certificates matter?
A digital certificate connects a public key with an identity or subject through a trust mechanism. Microsoft’s official module includes the concept and use of digital certificates, so certificate purpose belongs in the core study plan even though the supplied facts do not provide a full certificate standard, field list, or validation procedure.
The practical problem is identity binding. A public key by itself does not tell a recipient whose key it is. A certificate helps a relying party evaluate that association within a trust model. Study the difference between a key, a certificate, and a digital signature: the key performs or verifies a cryptographic operation; the certificate provides identity-related context for a public key; the signature provides evidence tied to signed data.
Create a chain-of-purpose exercise. Start with a server or person that has a key pair. Ask how another party obtains the public key, how it evaluates the associated identity, and how a signature can be checked. If your explanation jumps directly from “certificate” to “encrypted,” correct it: certificates are not simply another name for ciphertext.
The supplied Microsoft module places digital certificates after encryption, hashing, and digital signing in its learning sequence. That is a sensible study order because certificate questions are easier once you understand the operations and keys that certificates help support. It is a learning sequence, not evidence of the exam’s question order.
How should you study trust without overreaching?
Learn the certificate’s purpose and the need to evaluate trust, but do not invent a particular certificate authority hierarchy, revocation workflow, or protocol requirement. None of those details is established in the supplied research for this exam.
Write two answers: one for “What does the certificate help a recipient learn?” and one for “What does the certificate not do by itself?” The second answer should prevent category errors. A certificate does not replace key protection, does not automatically make a weak algorithm secure, and does not by itself satisfy every confidentiality or integrity requirement.
What study sequence is most efficient?
Use a layered sequence that moves from purpose to mechanism to scenario. First learn the security goals and plaintext/ciphertext vocabulary. Next compare symmetric and asymmetric key relationships. Then study hashing, MACs, signatures, and certificates. Finish by applying the concepts to communication, storage, and key-management decisions.
This order follows the dependencies in the supplied sources. Microsoft begins with basic concepts and proceeds through encryption, hashing and digital signing, and digital certificates. AWS supplies the goal-and-tool framework, while EC-Council’s beginner course provides a useful list of named topics. Read broadly once, then spend most of your time retrieving and applying the ideas without notes.
Do not begin with a list of algorithms. Algorithm-first preparation often produces recognition without reasoning: a learner may know that AES is symmetric but still choose encryption when a scenario asks for sender authentication or integrity evidence. Start each study session with a requirement and select the mechanism afterward.
Separate confirmed facts from recommendations in your notes. Mark Microsoft, AWS, EC-Council, and Splunk statements as source-backed learning material. Mark your own diagrams, mnemonics, and scenario answers as study aids. Keep all exam-format assumptions in a separate “unconfirmed” list so they do not quietly become supposed requirements.
Roadmap: foundation phase
In the foundation phase, define cryptography, plaintext, ciphertext, encryption, decryption, key, confidentiality, integrity, authentication, and non-repudiation in your own words. Then explain why availability may be part of the broader security context without claiming that encryption alone provides it.
Use the Microsoft Learn module for a structured first pass. It labels itself beginner-level and covers basic concepts, encryption, hashing, digital signing, and digital certificates. After each unit, close the page and produce a short explanation from memory. Mark any term you can recognize but cannot explain as a review target.
Roadmap: mechanism phase
In the mechanism phase, draw two diagrams: one for a shared-key exchange and one for a public/private-key relationship. Add a separate diagram for a hash and a separate one for a signature. Label the information, key roles, transformation, and verification step.
Use AWS for the symmetric/asymmetric comparison and cryptographic goals. Use the EC-Council course description as a checklist for AES, RSA, Diffie-Hellman, elliptic-curve cryptography, hashing, and digital signatures. Use Splunk to reinforce algorithm categories and the role of key management. Do not treat a course description as an exam blueprint.
Roadmap: application phase
In the application phase, solve short scenarios without looking at notes. For each one, identify the security requirement, select a mechanism, name the key relationship, and state a limitation or remaining question. Example prompts can involve protecting stored information, detecting an altered message, authenticating a sender, or establishing confidence in a public key.
Include scenarios that require more than one control. A message may need confidentiality and integrity; a public key may need identity context; a bulk-data design may need efficient symmetric protection while using asymmetric techniques for a related exchange. The point is to explain the combination, not to claim that one tool solves every problem.
Roadmap: verification phase
In the verification phase, take a blank sheet and reconstruct the complete map from memory. Define each security goal, compare the two key models, distinguish hash/MAC/signature/encryption, and explain the role of a certificate. Then consult the sources and correct only the gaps that matter.
Your readiness decision should be based on explanation and application, not on a percentage from an unofficial quiz. Because no official exam score or blueprint is supplied here, there is no evidence-based numerical threshold to report. Schedule only after confirming the actual exam requirements and deciding that your knowledge is stable under unfamiliar wording.
How can you turn reading into exam-ready recall?
Replace passive rereading with retrieval, comparison, and correction. A useful session produces an explanation, a diagram, or a scenario decision that you can inspect for errors. Reading the same definition repeatedly can create familiarity without proving that you can distinguish similar mechanisms under pressure.
Build a compact concept matrix with rows for encryption, hashing, MACs, digital signatures, certificates, symmetric cryptography, and asymmetric cryptography. Use columns for primary purpose, key arrangement, reversible or non-reversible outcome where relevant, what a recipient can verify, and a common misuse. Leave some cells blank initially and fill them from memory.
Use paired questions. Ask “Does this hide the content?” and “Does this prove who sent it?” Ask “Is the same key used?” and “Is a public/private relationship involved?” Ask “Can the recipient verify a change?” and “How is identity associated with a public key?” Paired questions force the distinctions that introductory assessments often test.
Explain one concept aloud in plain language, then explain it again using the terms plaintext, ciphertext, key, digest, signature, or certificate where appropriate. If the technical version becomes less accurate than the plain-language version, simplify the explanation rather than adding jargon.
When reviewing a wrong answer, classify the error: wrong goal, wrong key model, wrong operation, or unsupported assumption. This diagnosis tells you what to study next. Merely recording the correct option does not repair the reasoning that caused the mistake.
Which hands-on activities are safe and useful?
Use reversible, educational exercises that demonstrate concepts rather than attempting to reproduce exam content. You can diagram a message flow, calculate or inspect a digest with a permitted learning tool, compare a shared-key and public-key workflow, or inspect how a certificate associates a subject with public-key information.
Keep the exercise tied to a question. For example, change one character in a sample message and observe that the digest comparison no longer matches; then explain why that demonstrates an integrity check rather than confidentiality. If you inspect a signature, explain verification separately from encryption. Do not use leaked questions, dumps, or memorized answer sets as a substitute for understanding.
How should flashcards be written?
Write contrastive cards instead of isolated vocabulary cards. “What is AES?” is weaker than “Why would AES be classified as symmetric, and what key relationship does that imply?” “What is a certificate?” is weaker than “What identity-related problem can a certificate help address, and what does it not replace?”
Keep one decision per card. Include the answer in your own words, a source link, and a warning about a likely confusion. Retire a card only after you can answer it correctly in more than one scenario, not merely after recognizing the wording.
What mistakes most often undermine preparation?
The most damaging mistake is treating all cryptographic terms as synonyms. Encryption, hashing, signing, authentication, certificates, and key exchange may appear together in a system, but they are not interchangeable. The remedy is to state the security requirement before naming a mechanism.
Another mistake is learning key sizes as if they were universal recommendations. The supplied research gives specific AES key-size and block-size facts and mentions a 56-bit key length in the Splunk material, but it does not establish a complete modern selection policy for this exam. Record supported numbers with their exact subject and avoid turning isolated facts into blanket guidance.
Do not confuse a certificate with a public key, or a public key with a digital signature. The certificate provides identity-related context for a public key; the signature is an operation or result that can be verified against signed data. The key pair supplies cryptographic roles. Keeping those three ideas separate improves both scenario reasoning and terminology.
Do not assume that a course’s beginner label proves the exam has no difficult questions. Beginner coverage describes the learning material, not the examination’s item wording or scoring. Prepare for clear fundamentals expressed through unfamiliar scenarios.
Do not infer exam delivery from a learning module. The Microsoft page describes an online training module and a module assessment, but that does not confirm how Introduction-to-Cryptography is delivered. Treat training access and exam registration as separate decisions.
Finally, do not schedule from a third-party page that lacks official confirmation. Unverified claims about price, timing, score, question count, languages, or availability can create avoidable cost and deadline problems. Confirm the live official listing first.
How do you handle conflicting explanations?
Prefer the supplied official or publisher source for the narrow fact it actually states, then preserve the scope of that statement. If one source explains a general principle and another lists a training topic, do not merge them into an unsupported exam requirement.
When a source uses a simplified beginner explanation, retain the useful model but add a boundary in your notes. For example, encryption addresses confidentiality, but a complete communication design may also require integrity and authentication. This approach keeps your answer accessible without making it technically absolute.
What delivery and scheduling information should you verify?
The supplied research does not evidence the Introduction-to-Cryptography exam’s delivery method, duration, registration route, price, language options, prerequisites, score, question count, or current availability. Make those confirmations part of preparation rather than filling the gaps with assumptions from Microsoft Learn or another provider.
Use the official exam-owner page linked from the catalogue record, if one is available, and check the page immediately before scheduling. Confirm the exact exam title and identifier, eligibility or prerequisite rules, delivery choices, identification requirements, rescheduling and retake terms, and any permitted resources. If the page does not state an item, contact the provider or leave it unconfirmed.
The Microsoft module offers Azure account information and an assessment within the training module. That is useful learning context, but it is not evidence that the Introduction-to-Cryptography exam requires Azure, uses the module assessment, or follows Microsoft’s assessment rules. Similarly, EC-Council’s beginner course is evidence of topic coverage, not evidence of this exam’s provider or delivery.
Do not use the absence of public details as a reason to guess. A candidate can make a sound preparation decision without knowing the format, but cannot make a sound booking decision without confirming the booking conditions. Keep study planning moving while you verify scheduling facts.
What should you ask before booking?
Ask the official provider five practical questions: Is this the current examination associated with the catalogue identifier? What prerequisites apply? How is it delivered? What are the current fee, duration, language, and retake rules? Where is the official objective outline? Record the answers and the date you checked them.
If an exam page supplies a blueprint, rebuild your study plan around its named domains and weights. Until then, do not label the topic groups in this guide as official domains and do not calculate a target study percentage from the available sources.
How should you use the official sources?
Use each source for a defined study job. Microsoft Learn supplies a beginner-friendly progression through basic concepts, encryption, hashing and digital signing, and certificates. AWS supplies concise distinctions among goals, encryption types, and cryptographic tools. EC-Council supplies a beginner topic checklist. Splunk provides broader explanations, named algorithms, use cases, and key-management context. IBM is useful as an additional cryptography reference, but the supplied research summary does not provide specific IBM technical facts to treat as verified here.
Read Microsoft first if the subject is new. Its learning objectives give you a bounded foundation and its module assessment can expose terminology gaps. Do not interpret passing that module assessment as passing or predicting the external exam; the page describes it as an assessment for the module.
Read AWS next to sharpen mechanism selection. Use its descriptions of the four primary goals, symmetric and asymmetric cryptography, and cryptographic tools to build your comparison table. Write a scenario answer after each reading rather than collecting quotations.
Use EC-Council after the fundamentals to check named-topic coverage. Its beginner course explicitly includes AES, RSA, Diffie-Hellman, elliptic-curve cryptography, hashing, and digital signatures. Treat the list as a revision checklist and not as proof of exam weighting, question count, or required depth.
Use Splunk to connect concepts to use cases and key management. Its material discusses protection of data at rest, communication, and data in use; explains plaintext and ciphertext; and identifies key generation, distribution, and rotation as management tasks. Verify every numeric or algorithm-specific note against the exact source wording before putting it in a study sheet.
Use IBM only for supplementary orientation unless you independently confirm a specific claim on the linked page. More sources do not automatically create a more accurate exam outline. The official exam page remains the authority for objectives and scheduling.
How should your notes cite evidence?
Put the source URL beside each fact that might be tested: a definition, a named algorithm, a learning objective, or a key-size statement. Put “recommendation” beside your own study advice. Put “unconfirmed” beside every exam-format detail not published by the official provider.
This simple labeling prevents a frequent preparation failure: a learner remembers a training example or a third-party claim and later treats it as an official requirement. Evidence labels make it easier to revise your plan when the exam owner publishes or changes its outline.
What should you do in the final review?
The final review should test distinctions and decisions, not introduce a new pile of terminology. Reconstruct the security-goal map, compare key models, explain the four core cryptographic functions, and walk through a certificate-based trust question. Then verify the booking details from the official source.
Use a short final checklist: Can you define plaintext and ciphertext? Can you distinguish symmetric from asymmetric keys? Can you explain why bulk data may call for symmetric protection? Can you separate hashing, MACs, and signatures? Can you state what a certificate contributes? Can you explain why key management matters? Can you identify which claims remain unconfirmed for this exam?
Review any numeric facts only with their labels. The supplied research states that AES key sizes can be 128, 192, and 256 bits and that AES encryption occurs in blocks of 128 bits each. It also states that RSA is an asymmetric algorithm and that the Splunk article mentions a 56-bit key length in its discussion of an algorithm. Do not copy a number into a generic “recommended key size” list unless the source attaches that recommendation to a specific algorithm and context.
Avoid last-minute memorization of dumps or leaked material. Such material is not a reliable measure of understanding, may be inaccurate or unauthorized, and cannot establish that you can apply the concepts to a new scenario. Use source-based explanations and legitimate practice instead.
After the review, make one of two decisions. If you can explain and apply the concepts and the official booking details are confirmed, schedule according to your own availability and the provider’s rules. If you still confuse mechanisms or cannot confirm the exam conditions, continue targeted study and verification rather than booking on an assumption.
What is the next action after reading this guide?
Open the official exam listing associated with Introduction-to-Cryptography and record its current objectives and scheduling rules. Then create the concept matrix, complete the Microsoft foundation module, and test yourself with scenario explanations using AWS and the other supplied references. End the first session by identifying three gaps; those gaps should determine the next study block.
Conclusion
Prepare for Introduction-to-Cryptography as a reasoning exam until an official blueprint says otherwise. Master the security goals first, then the symmetric and asymmetric key models, followed by hashing, MACs, signatures, certificates, algorithms, and key management. Keep source-backed facts separate from study recommendations and unconfirmed exam logistics. Your final decision is twofold: confirm the provider’s current requirements, and schedule only when you can select and explain mechanisms for unfamiliar security scenarios.
Related exams
- Accounting-for-Decision-Makers exam — WGU Accounting for Decision Makers C213 VAC2
- Applied-Algebra exam — WGU Applied Algebra FXO2 PFXP C957
- Cloud-Deployment-and-Operations exam — WGUCloud Deployment and Operations
- Cybersecurity-Architecture-and-Engineering exam — WGU Cybersecurity Architecture and Engineering (D488)
- Data-Driven-Decision-Making exam — VPC2 Data-Driven Decision Making C207
- Data-Management-Foundations exam — WGU Data Management – Foundations Exam
