Sign in
Home/ISACA/Certificate of Cloud Auditing Knowledge (CCAK)/Free questions

Certificate of Cloud Auditing Knowledge (CCAK) — Free Practice Questions

10 free sample questions from a bank of 258, with the correct answers and explanations. No signup required — start practising right now.

1Changes to which of the following will MOST likely influence the expansion or reduction of controls required to remediate the risk arising from changes to an organization’s SaaS vendor?
  • Risk exceptions policy
  • Contractual requirements
  • Risk appetite
  • Board oversight
Answer: B

The short version

B — Contractual requirements decide the control set. When the SaaS vendor changes, the contract decides what you can demand, verify and enforce, so the remediation controls must expand or shrink to match those terms.

Key concepts in this question

  • Contractual requirements: enforceable duties in the agreement such as security controls, service levels, audit rights, data handling, breach notice and exit assistance.
  • Risk exception policy: a governance path to formally accept a known gap for a time, not a driver that rescales the whole control set.
  • Risk appetite: the broad enterprise tolerance set by leadership that frames all risk talk but does not by itself rewrite vendor-specific controls.
  • Board oversight: governance attention and escalation that enables action but does not define the detailed remediation controls.

Why B is correct

Contract terms directly fix the boundary of responsibility between customer and SaaS provider, including which security functions the provider must deliver and what evidence the customer may inspect. A new or changed vendor brings different service commitments,. That linkage makes the contract the most immediate. Appetite and oversight shape willingness to accept residual risk, but only the agreement changes what is enforceable day to day.

Why the others are wrong

  • A. Risk exceptions document temporary acceptance and conditions, they do not create the underlying control obligation tied to a new vendor.
  • C. Risk appetite sets enterprise tolerance in general terms, it does not translate a specific vendor change into specific added or removed controls.
  • D. Board oversight provides direction and accountability, but the board does not rewrite the operational and assurance controls that flow from contract language.

CCAK exam tip

Think contract first for vendor change: new vendor equals new promises, so map clauses to controls before debating appetite or governance.

2When a client’s business process changes, the CSP SLA should:
  • be reviewed, but the SLA cannot be updated.
  • not be reviewed, but the cloud contract should be cancelled immediately.
  • not be reviewed as the SLA cannot be updated.
  • be reviewed and updated if required.
Answer: D

The short version

D — Review the SLA and update it when client needs change. An SLA is a living instrument, so a material business change must trigger review and revision to keep services and duties aligned.

Key concepts in this question

  • SLA lifecycle: SLAs are negotiated, monitored, reviewed and amended as business needs, volumes, risk and technology evolve, by mutual agreement.
  • Business alignment: Cloud value depends on fit to actual processes, service levels, capacity, support hours and reporting needs, all of which can shift when the client reorganises or new offerings.
  • Shared responsibility clarity: The SLA records who does what, to what target, with what remedy, so stale targets create disputes, under-provisioning or overpayment.
  • Contract governance: Review does not mean unilateral cancellation, it means assessing impact, renegotiating SLOs, credits, pricing and exclusions through defined change control.

Why D is correct

D is correct because CCAK and cloud governance guidance treat SLA management as continuous. When the process changes, both parties must re-examine scope, targets, support and compliance, then update terms that no longer fit. This keeps terms enforceable and measurable, with a clear basis for monitoring and improvement.

Why the others are wrong

  • A. Review without any possibility of update defeats the purpose of review and contradicts standard change control, which allows amendment by agreement.
  • B. Refusing review and immediately cancelling the contract is disproportionate, disruptive and commercially unsound when adjustment would suffice.
  • C. Claiming no review is needed ignores that SLAs must stay aligned to business objectives, risk appetite and regulatory duties as they evolve.

CCAK exam tip

Think living SLA: business changes, so review then revise by agreement, never freeze or jump straight to termination.

3When building a cloud governance model, which of the following requirements will focus more on the cloud service provider’s evaluation and control checklist?
  • Security requirements
  • Legal requirements
  • Compliance requirements
  • Operational requirements
Answer: A

The short version

A — Security requirements drive provider evaluation. In a cloud governance model the security lens produces the checklist used to judge the provider, while legal, compliance and operational lenses serve different purposes.

Key concepts in this question

  • Security requirements: core protection capabilities expected from the platform.
  • Legal requirements: contract enforceability, jurisdiction, liability, intellectual property and e-discovery duties handled with counsel.
  • Compliance requirements: mapping to external obligations such as standards and regulations and the evidence needed to prove conformity.
  • Operational requirements: day to day service behavior such as performance and support.

Why A is correct

Security requirements translate into concrete control questions the customer puts to the provider, such as how access is provisioned, how data is isolated and encrypted, how networks are segmented, how vulnerabilities are patched and how incidents are detected and reported. Those questions form an evaluation checklist. That is why the study material places provider evaluation under the security requirements workstream.

Why the others are wrong

  • B. Legal requirements focus on rights, obligations and enforceability, not on the technical evaluation of provider safeguards.
  • C. Compliance requirements focus on satisfying external rules and producing attestation, which builds on but is broader than the provider control checklist.
  • D. Operational requirements focus on running and supporting the service reliably, not on judging the adequacy of the security control set.

CCAK exam tip

Link security to supplier checklist, legal to contract, compliance to evidence, operations to run-the-service when the stem asks which lens evaluates the provider.

4Prioritizing assurance activities for an organization’s cloud services portfolio depends PRIMARILY on an organization’s ability to:
  • schedule frequent reviews with high-risk cloud service providers.
  • develop plans using a standardized risk-based approach.
  • maintain a comprehensive cloud service inventory.
  • collate views from various business functions using cloud services.
Answer: B

The short version

B — Prioritise assurance with a standardised risk-based plan. Limited audit resources must target highest likelihood and impact, so prioritisation needs a consistent risk method, not ad-hoc scheduling.

Key concepts in this question

  • Risk-based assurance: Frequency, depth and method of reviews are scaled to inherent risk, data sensitivity, criticality, threat landscape and prior findings.
  • Standardised approach: A common taxonomy, scoring model and planning process lets the organisation compare IaaS, PaaS and SaaS services fairly across business units.
  • Portfolio view: Assurance covers many providers and deployment models, requiring triage rather than equal effort for every service.
  • Inventory as input: A service catalogue is necessary for visibility but does not by itself tell you what to audit first or how deeply.

Why B is correct

B is correct because CCAK places risk assessment at the centre of cloud audit planning across deployment models, service models and data classification. The organisation lists foreseeable cloud risks, evaluates each service against likelihood, impact and tolerance, then builds the plan from that analysis. Inventories and stakeholder views feed the plan, but only a standard risk approach makes it repeatable and defensible.

Why the others are wrong

  • A. Scheduling frequent reviews only with high-risk providers assumes you already know who is high risk and skips the method for deciding that ranking.
  • C. Maintaining a comprehensive inventory is foundational for visibility but does not rank risk or set assurance depth and timing.
  • D. Collating views from business functions informs context but without a standard risk model it remains anecdotal and inconsistent.

CCAK exam tip

For prioritise or FIRST in assurance planning, choose the standardised risk assessment, inventory and opinions are only inputs.

5If the degree of verification for information shared with the auditor during an audit is low, the auditor should:
  • reject the information as audit evidence.
  • stop evaluating the requirement altogether and review other audit areas.
  • delve deeper to obtain the required information to decide conclusively.
  • use professional judgment to determine the degree of reliance that can be placed on the information as evidence.
Answer: D

The short version

The answer is D, use professional judgment to determine the degree of reliance that can be placed on the information as evidence. CCAK Study Guide page 284 states this rule for low verification evidence such as uncorroborated interviews without artifacts. The exam tests verbatim guide language, so D beats the plausible delve deeper option.

Key concepts in this question

This tests audit evidence reliability, verification levels, corroboration, and professional judgment in cloud audits. Verification is higher when artifacts or a second person confirm a claim. It is low for lone interviews or unconfirmed process claims. CCAK expects auditors to weigh such evidence, not auto accept or auto reject it, and to document the reliance decision.

Why D is correct

D repeats the CCAK page 284 sentence almost word for word. When verification is low, the guide directs the auditor to use judgment to decide how much reliance is reasonable. Generic ISA logic about gathering more evidence does not override the specific CCAK rule the exam keys to. Community comments citing page 284 confirm D with the corroborating account example.

Why the others are wrong

A is wrong because rejection is too extreme and wastes context that can inform risk assessment when weighted properly. B is wrong because stopping evaluation abandons the audit objective. C is wrong because delving deeper is good practice but not the guide stated response for this trigger phrase, so it is a distractor confusing thoroughness with judgment.

CCAK exam tip

When you see degree of verification is low, choose professional judgment and reliance language. Memorize the page 284 trigger pair and do not pick delve deeper unless the stem asks about insufficient evidence generally.

6Which best describes the difference between a type 1 and a type 2 SOC report?
  • A type 2 SOC report validates the operating effectiveness of controls whereas a type 1 SOC report validates the suitability of the design of the controls.
  • A type 2 SOC report validates the suitability of the design of the controls whereas a type 1 SOC report validates the operating effectiveness of controls.
  • A type 1 SOC report provides an attestation whereas a type 2 SOC report offers a certification.
  • There is no difference between a type 2 and type 1 SOC report.
Answer: A

The short version

A — Type 2 tests effectiveness over time, Type 1 tests design at a point. Type 1 asks whether the design looks suitable, Type 2 asks whether the controls actually operated effectively through the review period.

Key concepts in this question

  • Suitability of design: whether a control as described should achieve its objective if operated as designed, judged at a point in time.
  • Operating effectiveness: whether the control ran consistently, by the right people, with expected results across the whole audit period.
  • Attestation vs certification: SOC reports are independent attestation opinions on controls, not product certifications of general quality.
  • SOC family scope: SOC 1 covers controls relevant to financial reporting, SOC 2 covers trust services criteria, while Type 1 versus Type 2 describes depth of testing.

Why A is correct

A Type 1 report gives an opinion on the fairness of the system description and the suitability of control design as of a specific date, without testing operation over time. A Type 2 report adds testing of operating effectiveness across a period. That period coverage is what cloud customers need for. The distinction holds across SOC 1 and SOC 2, even though the subject matter differs. Reversing the two or calling one a certification misstates the assurance model.

Why the others are wrong

  • B. This reverses the standard meanings, Type 1 never proves operation over time and Type 2 never stops at design alone.
  • C. Both Type 1 and Type 2 are attestation engagements, neither converts to a certification simply by changing type number.
  • D. The difference is fundamental and affects reliance, so claiming no difference ignores period testing versus point-in-time design review.

CCAK exam tip

Remember 1 equals design at a date, 2 equals design plus operation across a period, and both SOC types are attestations, never certifications.

7You have been assigned the implementation of an ISMS, whose scope must cover both on premise and cloud infrastructure. Which of the following is your BEST option?
  • Implement ISO/IEC 27002 and complement it with additional controls from the CCM.
  • Implement ISO/IEC 27001 and complement it with additional controls from ISO/IEC 27017.
  • Implement ISO/IEC 27001 and complement it with additional controls from ISO/IEC 27002.
  • Implement ISO/IEC 27001 and complement it with additional controls from the NIST SP 800-145.
Answer: B

The short version

B — Build the ISMS on ISO 27001 and add ISO 27017 for cloud. ISO 27001 supplies the certifiable management system for all scopes, while ISO 27017 supplies cloud-specific implementation guidance for both provider and customer to cover on-premise plus cloud.

Key concepts in this question

  • ISO 27001 as ISMS specification: Defines scope, risk assessment, Statement of Applicability, controls, internal audit and continual improvement in a certifiable form.
  • ISO 27002 as control catalogue: Describes how generic controls can be implemented to support a 27001 ISMS, but is not itself the management system.
  • ISO 27017 as cloud extension: Adds shared-roles guidance, segregation, virtual machine hardening, cloud monitoring, alignment of security management for cloud services.
  • Hybrid scope: On-premise plus cloud needs one ISMS with consistent governance plus tailored cloud controls, not two disconnected programmes.

Why B is correct

B is correct because only ISO 27001 establishes an ISMS you can scope to hybrid infrastructure and certify. ISO 27017 supplements ISO 27002 for cloud, clarifying shared roles and measures for the 27001 treatment plan. CCM only maps controls and SP 800-145 only defines cloud, so neither gives an ISMS plus cloud set.

Why the others are wrong

  • A. ISO 27002 alone is a code of practice, not an ISMS specification, so it cannot be certified and misses management system elements.
  • C. Adding only ISO 27002 to ISO 27001 covers generic controls but omits cloud-specific shared-responsibility and virtualisation guidance.
  • D. NIST SP 800-145 is a cloud definition document, not a control supplement for operating an ISMS.

CCAK exam tip

ISMS equals 27001, generic how equals 27002, cloud how equals 27017, memorise that trio for hybrid scope questions.

8As a developer building codes into a container in a DevSecOps environment, which of the following is the appropriate place(s) to perform security tests?
  • Within developer’s laptop
  • Within the CI/CD server
  • Within version repositories
  • Within the CI/CD pipeline
Answer: D

The short version

D — Put security tests inside the CI/CD pipeline. In DevSecOps, automated checks must run consistently at code, build, image and deploy stages, and only pipeline integration guarantees every container build is tested the same way without slowing delivery.

Key concepts in this question

  • Shift-left plus continuous: Security moves early and repeats often, combining SAST, SCA, image scanning, DAST and policy gates.
  • Pipeline as enforcement point: The pipeline orchestrates checkout, build, test, scan, sign and promote, with quality gates that can fail the build.
  • Container specifics: Base-image vulnerabilities, secrets in layers, misconfigurations and over-privileged defaults demand automated image and IaC scanning on each build.
  • Laptop and server limits: Local or server-only testing is ad-hoc, bypassable and inconsistent across developers and branches.

Why D is correct

D is correct because the CI/CD pipeline is the single chokepoint every change must pass, making it the right place to embed automated security tests with consistent tooling, thresholds and evidence. Tests trigger on commit and pull request, scan code, dependencies, Dockerfiles and built images, block promotion on critical findings, and log results for audit. This keeps DevOps speed while making security continuous and auditable, which isolated checks cannot assure.

Why the others are wrong

  • A. Laptop testing depends on individual discipline and tool versions, so coverage varies and bypass is easy.
  • B. Testing only on the CI/CD server without pipeline integration lacks stage gates, versioned policy and automatic blocking of tainted artefacts.
  • C. Version repositories store code and can trigger checks, but storage alone does not execute staged tests or enforce promotion rules.

CCAK exam tip

DevSecOps test location equals the pipeline, where automation, gates and evidence meet for every build.

9An organization that is utilizing a community cloud is contracting an auditor to conduct a review on behalf of the group of organizations within the cloud community. From the following, to whom should the auditor report the findings?
  • Public
  • Management of organization being audited
  • Shareholders/interested parties
  • Cloud service provider
Answer: C

The short version

C — Report community-cloud findings to the interested parties. When one audit serves several sharing organisations, results must go to the collective beneficiaries bearing the shared risk.

Key concepts in this question

  • Community cloud model: Infrastructure is shared by organisations with common mission, compliance or security needs, with joint governance.
  • Engagement principal: The auditor reports to the engaging client group, respecting confidentiality, agreed distribution and use limitations.
  • Shareholders and interested parties: In CCAK usage this means the member organisations relying on the shared environment, not the general public.
  • Provider versus customer reporting: Findings about the shared platform affect all tenants, so siloed reporting to one manager or to the provider alone is insufficient.

Why C is correct

C is correct because the audit was contracted on behalf of the group within the community cloud, making the member organisations the joint owners of the assurance. Reporting to interested parties ensures each member understands shared status, residual risk and remediation. Public disclosure would breach confidentiality, while reporting only to one manager or only to the provider would deny other relying parties the information they paid for and need for their own risk decisions.

Why the others are wrong

  • A. Public reporting overexposes sensitive findings and violates engagement confidentiality and distribution agreements.
  • B. Reporting only to management of the organisation being audited ignores the other community members who share risk and sponsorship.
  • D. Reporting only to the provider confuses the subject of the review with the client and leaves customer organisations uninformed.

CCAK exam tip

Community audit equals community report, deliver to the member interested parties who share the cloud and the risk.

10Which of the following parties should have accountability for cloud compliance requirements?
  • Customer
  • Equally shared between customer and provider
  • Provider
  • Either customer or provider, depending on requirements
Answer: A

The short version

A — The customer keeps accountability for compliance. Controls and tasks can be delegated to a provider, but legal and regulatory accountability for meeting obligations stays with the organisation that owns the data and business duty.

Key concepts in this question

  • Accountability versus responsibility: Responsibility is who performs a control, accountability is who must answer if compliance fails and it cannot be outsourced away.
  • Shared responsibility model: Provider secures the platform, customer secures data, access, configuration and compliance use, with boundaries varying by IaaS, PaaS and SaaS.
  • Regulatory reality: Laws target the data controller and owner, expecting due diligence, contracts, monitoring and evidence regardless of outsourcing.
  • Contract limits: SLAs, certifications and attestations support assurance but do not transfer legal liability for non-compliance.

Why A is correct

A is correct because CCAK stresses repeatedly that accountability is retained by the customer irrespective of service or deployment model. The customer must identify applicable requirements, assign controls, obtain assurance over provider controls, and demonstrate compliance to regulators and stakeholders. Sharing or shifting that ultimate answerability to the provider contradicts both guidance and law, which hold the owner accountable even when execution is delegated.

Why the others are wrong

  • B. Equal sharing misstates the model, duties may be split but ultimate accountability is not split fifty-fifty.
  • C. Placing accountability solely on the provider ignores that the customer chooses the service, configures use and remains liable for outcomes.
  • D. Making it pivot purely on requirements confuses task allocation, which can vary, with accountability, which remains with the customer.

CCAK exam tip

Memorise the mantra: responsibility can be shared or transferred, accountability never leaves the customer.

Want the full bank of 258 questions for Certificate of Cloud Auditing Knowledge (CCAK)? See all practice exams.