Certification Exam Preparation Resources

Knowledge areas

• Module structure and dependency injection
• Catalog data model, EAV attributes and product types
• Checkout, quote and order flow customization
• Plugins, observers, events and preferences
• REST and GraphQL API integration
• Theme layout, blocks and templates
• Caching, indexing and performance tuning
• Configuration scopes and admin permissions

Suggested approach

Work in a local Commerce instance rather than reading only. Build a small module that adds a custom order attribute, expose it through the API, then trace how cache and index invalidation affect what the storefront returns.

Knowledge areas

• PCI DSS v4.x requirement families and intent
• Assessment procedures, evidence and testing methods
• Scope definition and network segmentation validation
• Compensating controls and the customised approach
• Report on Compliance and Attestation of Compliance
• Requirement 8 identity, authentication and MFA
• Requirement 10 logging, monitoring and time sync
• Secure software development and vulnerability management

Suggested approach

Map each requirement family to its testing procedures and write down the evidence you would collect as an assessor. Practise scoping decisions, because determining what is inside the cardholder data environment drives almost every later judgement.

Knowledge areas

• Realms, instances, sites and multi storefront topology
• Catalog, pricing, promotions and inventory design
• Order management and OCAPI or Commerce API integration
• LINK cartridges and third party integrations
• Page Designer, content slots and SEO structure
• Sandbox, staging and production environments
• Caching strategy and storefront performance
• Roles, permissions and account security

Suggested approach

Prepare to justify decisions, not to recall menus. Sketch a multi site and multi locale storefront, then explain how caching, search, promotions and integration points behave when traffic scales or a partner service fails.

Knowledge areas

• Ledgers, business units and chart of accounts design
• Subledger accounting and journal creation
• Payables, receivables and cash management basics
• Period close and reconciliation routines
• Financial reporting and inquiry tools
• Approval routing and internal controls
• Configuration versus customization decisions
• Data security roles in financial applications

Suggested approach

Follow one transaction end to end, for example an invoice through payment, subledger accounting and into the general ledger. Understanding that chain makes configuration questions much easier to reason through.

Knowledge areas

• Certificate lifecycle, enrollment and renewal
• CRL distribution points and OCSP behaviour
• Internal Certificate Authority operations
• IKE and IPSec certificate based authentication
• Trust chains and validation failures
• Object and policy management in SmartConsole
• Expired or revoked certificate troubleshooting
• Clock synchronisation and log correlation

Suggested approach

Draw a small PKI map for your own lab and walk through what happens when a gateway certificate expires mid session. Check Point specific behaviour around management objects matters as much as generic PKI theory.

Knowledge areas

• Kubernetes control plane and node components
• Pods, deployments, services and workloads
• Container images, registries and runtimes
• Cluster networking, CNI, ingress and DNS
• Volumes, persistent storage and storage classes
• Configuration, secrets and environment injection
• Scheduling, node selectors, requests and limits
• Observability, RBAC basics, Helm and GitOps

Suggested approach

Install a local cluster with kind or minikube and run kubectl until the vocabulary feels physical. Deploy an app, expose it, read its logs, and deliberately break a pod to see how the controller responds.

Knowledge areas

• macOS setup, user accounts and iCloud services
• Device management, profiles and MDM enrollment
• Apple Business Manager and supervision
• FileVault, Gatekeeper, firewall and privacy controls
• Networking, certificates and VPN configuration
• Diagnostics, recovery, restore and safe mode
• Mail, calendar and collaboration services
• Issue triage, documentation and escalation

Suggested approach

Rehearse real support flows such as a Mac that will not boot, an iPhone stuck at activation lock, or a managed profile that will not apply. Apple tests judgement in a support conversation as much as feature knowledge.

Knowledge areas

• Requisitions, purchase orders and receipts
• Supplier, site and payment terms setup
• Invoice types, matching and hold resolution
• Payment batches, formats and disbursement
• Prepayments and expense reports
• Subledger accounting and journal transfer
• Period close, accruals and reconciliation
• Audit trail and segregation of duties

Suggested approach

Learn the transaction path before the screens. When you know how a two way match differs from a three way match and why a hold appears, most configuration questions resolve themselves.

Knowledge areas

• Architecture Development Method phases and ADM cycle
• Architecture content, artifacts and building blocks
• Stakeholder management, views and viewpoints
• Requirements management and the Architecture Repository
• Business, data, application and technology architectures
• Architecture governance, boards and compliance
• Enterprise Continuum and architecture reuse
• Risk management and capability maturity

Suggested approach

Learn the ADM as a cycle with clear inputs and outputs for each phase. For the scenario section, practise identifying what the question is really asking and eliminate implausible answers using framework logic instead of recall.

Knowledge areas

• Business management and HR metrics
• Talent acquisition, selection and onboarding
• Learning, development and career planning
• Compensation structures and benefits programs
• Employee relations, discipline and labour law
• US employment statutes and compliance deadlines
• Health, safety, security and risk management
• HR information systems and analytics

Suggested approach

Build flashcards for the major US statutes, noting who is covered, key thresholds, filing deadlines and penalties. Then practise applying them to short workplace scenarios, which is how most items are framed.

Knowledge areas

• Splunk architecture, indexers, search heads and forwarders
• Data inputs, monitors and HTTP Event Collector
• props.conf, transforms.conf and inputs.conf precedence
• Field extraction, lookups, event types and tags
• Indexes, buckets, retention and frozen data
• Users, roles, capabilities, LDAP and SAML
• Search processing language, alerts and scheduled reports
• Indexer clustering and licence management

Suggested approach

Install a trial instance and ingest sample data. Trace one event from forwarder to parsing to index to search result, and learn the configuration file precedence order until it is automatic.

Knowledge areas

• Spine and leaf architecture and fabric design
• VLANs, VXLAN, EVPN and overlay networking
• Cisco NX-OS configuration and troubleshooting
• UCS compute, service profiles and hypervisor integration
• Fibre Channel, FCoE and storage networking
• Data center routing, BGP and first hop redundancy
• High availability, vPC and FabricPath behaviour
• Python, APIs and configuration automation basics

Suggested approach

Learn how a packet crosses the fabric, including VXLAN encapsulation and the control plane that builds the overlay. Practise reading NX-OS output, because troubleshooting items are usually diagnostic rather than definitional.

Knowledge areas

• OSI and TCP/IP models, cabling and switching
• VLANs, trunks, spanning tree and EtherChannel
• IPv4 and IPv6 addressing, subnetting and NAT
• Static routing, OSPF and path selection
• DHCP, DNS, SNMP, NTP and QoS
• ACLs, wireless architectures and device hardening
• Virtualisation, cloud and container concepts
• REST APIs, JSON and Cisco IOS automation

Suggested approach

Subnet until it is reflexive, then build packet tracer labs for switching and routing. Most candidates lose marks on troubleshooting items, so practise identifying the failing layer from a small set of symptoms.

Knowledge areas

• Subledger registration and source system setup
• Accounting method, journal entry rule set design
• Event classes, event types and transaction objects
• Chart of accounts mapping and value sets
• Journal import and reconciliation with source data
• Period close, reversal and adjustment handling
• Security roles and data access configuration
• Diagnostics, trace and error resolution

Suggested approach

Configure one simple subledger in a training environment and inspect the generated journals. Rule sets and mappings are the core of the exam, and hands on inspection makes the options much clearer.

Knowledge areas

• Cloud concepts, OCI regions and availability domains
• Compute shapes, images and autoscaling
• Object, block, file and archive storage options
• VCN design, subnets, gateways and security lists
• Identity and Access Management, policies and compartments
• Autonomous Database, Base Database and Exadata options
• Observability, notifications and event handling
• Cost management, budgets, tagging and support tiers

Suggested approach

Coverage matters more than depth here. Use the OCI Free Tier to create a VCN, launch an instance and store objects, then learn the differences between similar services so you can select the right one quickly.

Knowledge areas

• Solution positioning and business value
• Core technology vocabulary for the subject area
• Common customer use cases and objections
• Licensing, sizing and offering structure
• Competitive differentiation and partner roles
• Discovery questions and qualification criteria
• Deployment models and support options
• Exam format, duration and passing score

Suggested approach

Start from the official exam page and list the stated domains with their weightings. Role based exams reward applied judgement, so prepare short answers to scenario style questions about customer needs.

Knowledge areas

• Business analysis planning and elicitation techniques
• Stakeholder identification and communication
• Requirements gathering, documentation and validation
• Use cases, user stories and acceptance criteria
• Process modelling and gap analysis
• Solution evaluation and benefits tracking
• Agile and waterfall delivery contexts
• Traceability, change control and prioritisation

Suggested approach

Practise writing requirements that a developer and a stakeholder can both read. Take one real process you know, model the current state, define the future state, and justify the change with measurable benefits.

Knowledge areas

• Financial statements and the accounting cycle
• Accounts payable, receivable and payroll operations
• General ledger maintenance and period close
• Internal controls, segregation of duties and audit trails
• Budgeting, forecasting and variance analysis
• Cash management, treasury and reconciliation
• ERP and finance system configuration
• Compliance, ethics and data governance

Suggested approach

Anchor theory to a monthly close calendar. Work through reconciliation and control questions by asking what could go wrong in that step and which control would catch it.

Knowledge areas

• Genesys Cloud platform architecture and licensing
• Architect flows for inbound, outbound and in-queue calls
• Platform API usage, OAuth and authentication flows
• Data actions, integrations and web service calls
• Queues, skills, routing and ACD behaviour
• Telephony, edge devices and trunk configuration
• Reporting, analytics and notifications
• Sandbox, testing and deployment practices

Suggested approach

Build a small flow in a trial organisation and call one API endpoint from a script. Understanding how Architect, routing and the API layer connect covers a large share of developer level questions.

Knowledge areas

• Identity and access management, resource policies
• Resilient design with multi zone and auto scaling
• Compute selection across virtual, container and serverless
• Storage classes, lifecycle policies and durability
• Networking, subnets, peering and traffic control
• Database selection, caching and replication
• Cost optimisation, pricing models and tagging
• Operational tooling, migration and disaster recovery

Suggested approach

Practise mapping requirements to services and defending the trade off. Scenario items usually turn on two or three constraints, so identify them first, then choose the option that satisfies all of them.

Knowledge areas

• Implementation methodology and delivery phases
• Business process analysis and requirement mapping
• Configuration versus customisation decisions
• Data migration, cleansing and validation
• Integration patterns and middleware services
• Security roles, permissions and user provisioning
• Testing cycles, defect handling and cutover planning
• Training, documentation and support handover

Suggested approach

Confirm the exact product area and version on the vendor certification page, then study each delivery phase as a set of decisions with risks attached. Scenario questions usually test what you would do next, not what a screen looks like.

Knowledge areas

• BIG-IP system architecture and licensing
• Virtual servers, pools, members and monitors
• Load balancing methods and persistence profiles
• HTTP, TCP, SSL and compression profiles
• VLANs, self IPs, routes and SNAT
• Device groups, config sync and failover
• Application delivery services and DNS basics
• Backups, upgrades, logs and tcpdump analysis

Suggested approach

Draw the traffic path from client through virtual server, profile stack, pool and member, then learn what each object controls. Most troubleshooting items follow that path in reverse.

Knowledge areas

• IT service management and support processes
• Operating system and platform fundamentals
• Networking, connectivity and basic protocols
• Security awareness, access control and data handling
• Cloud and virtualisation concepts
• Troubleshooting method and root cause analysis
• Documentation, communication and escalation
• Exam format, duration and passing score

Suggested approach

Read the official exam outline first and allocate study time in proportion to the published weightings. Associate level exams reward clear reasoning over deep specialisation.

Knowledge areas

• Security Management Server and gateway architecture
• Access control policy, layers and rule base design
• Network objects, NAT rules and automatic NAT
• Threat prevention, IPS and Anti-Bot blades
• VPN configuration, communities and encryption
• Logging, monitoring and SmartConsole views
• Software blades, licensing and cluster setup
• Backup, upgrade and policy troubleshooting

Suggested approach

Build a two gateway cluster in a lab and push a policy with NAT and IPS enabled. Then break it on purpose and read the logs, because the exam leans heavily on identifying the cause of a failure from limited output.

Knowledge areas

• Advanced policy design, layered rules and inline layers
• Cluster XL, failover behaviour and state synchronisation
• Threat extraction, emulation and IPS tuning
• Advanced NAT, routing and VPN topology
• Identity Awareness and user based policy
• Scalable platforms, Maestro style concepts
• Performance profiling and bottleneck analysis
• Upgrade paths, migration and high availability design

Suggested approach

Study failure modes rather than features. Ask what happens during failover, what breaks when a policy is misordered, and how you would prove it from logs and cluster statistics.

Knowledge areas

• Analytics architecture, datasets and dataflows
• Data preparation, recipes and ETL patterns
• Dashboard and lens design for business users
• Query languages, computed fields and aggregations
• Security, sharing and row level access
• Performance tuning and dataset optimisation
• Einstein Discovery and prediction features
• Deployment between sandboxes and production

Suggested approach

Build a small end to end solution, from a source object through a recipe to a dashboard, and note where permissions change what a user sees. Consultant exams test design decisions and limits.

Knowledge areas

• Cilium architecture and eBPF fundamentals
• Networking, service load balancing and kube-proxy replacement
• Network policies, identity based rules and FQDN policies
• Hubble observability and flow visibility
• Service mesh integration and L7 visibility
• Cluster mesh and multi cluster connectivity
• Installation, configuration and upgrades
• Troubleshooting datapath and policy issues

Suggested approach

Deploy Cilium in a local cluster and inspect Hubble flows while you apply policies. Identity based networking behaves differently from IP based rules, and that difference is where most questions live.

Knowledge areas

• Application architecture and object relationships
• Configuration of ledgers, journals and postings
• Automation rules, flows and validation logic
• Security model, profiles and sharing rules
• Data import, mapping and error handling
• Integration with external financial systems
• Reports, dashboards and audit trails
• Deployment, change sets and release testing

Suggested approach

Set up a small configuration in a scratch org and walk a transaction from source record through to a journal entry. Automation and security questions are easier when you have seen the failure modes.

Knowledge areas

• Enterprise architecture and solution design patterns
• Data model design, sharing and large data volumes
• Integration patterns, middleware and event driven design
• Identity, single sign on and access architecture
• Performance, governor limits and platform limits
• DevOps, release management and environment strategy
• Governance, Centre of Excellence and standards
• Multi cloud and multi org considerations

Suggested approach

Practise defending trade offs out loud. Scenario questions usually contain two or three constraints that rule out attractive answers, so identify the constraints before comparing options.

Knowledge areas

• Solution architecture across sales, service and data clouds
• Data strategy, archiving and large data volume design
• Integration architecture and API governance
• Security architecture, encryption and event monitoring
• Scalability, caching and asynchronous processing
• Release management and deployment automation
• Technical debt, refactoring and design standards
• Multi org, multi cloud and M&A integration scenarios

Suggested approach

Check the current exam guide for the version differences, then prepare a short architecture narrative for one complex implementation you have worked on. Being able to explain why you chose a design is the skill being tested.

Knowledge areas

• Slack app architecture and manifest configuration
• Web API, Events API and Socket Mode
• Block Kit surfaces and interactive components
• OAuth scopes, tokens and permission models
• Workflow Builder steps and automation
• Slack Connect and external channel considerations
• Salesforce and Slack integration patterns
• Testing, distribution and app review requirements

Suggested approach

Build one working app that listens for an event, calls the Web API and renders a Block Kit message. Hands on experience with scopes and event subscriptions resolves most of the ambiguity in scenario questions.

Knowledge areas

• Analytics concepts, metrics and key indicators
• Data sources, joins and dataset structure
• Report types, filters and summarisation
• Dashboard components and layout best practice
• Chart selection and data storytelling
• Data quality, validation and cleansing
• Sharing, permissions and visibility rules
• Einstein Analytics fundamentals and next steps

Suggested approach

Build three reports and one dashboard against a sample dataset, then explain in one sentence what business question each answers. Foundations exams test interpretation as much as configuration.

Knowledge areas

• Standard and custom objects, fields and relationships
• Page layouts, record types and business processes
• Validation rules, flows and automation basics
• Profiles, permission sets and sharing model
• Data management, import and export routines
• Reports, dashboards and analytics access
• AppExchange, sandboxes and change sets
• Support processes, audit and troubleshooting

Suggested approach

Use a Trailhead playground or scratch org and configure one complete business process, including automation and sharing. Then explain what would break if a field were renamed or a profile removed.

Knowledge areas

• Advanced data model and relationship design
• Flow orchestration, error handling and debugging
• API access, connected apps and integration basics
• Large data volume and performance considerations
• Advanced sharing, roles and territory concepts
• Release awareness, sandbox strategy and testing
• Security review, audit and compliance settings
• Support tooling and issue isolation

Suggested approach

Compare this exam guide with the 201 line and study the differences first, since that is where new questions usually appear. Practise debugging a failing flow and reading the resulting error output.