Practice exams / CGE-P CGE-P practice exam 20 questions across the 7 exam domains, weighted like the real exam. Untimed. Submit to see your score by domain and an explanation for every answer. The real exam is 60 questions in 90 minutes and you pass at 72%. These questions are for practice and do not appear on the graded exam.
Question 1 of 20 · GRC Engineering Foundations A US SaaS company lands its first European enterprise prospect. The prospect's security team asks for an accredited certification of the company's information security management system. Which framework is the prospect asking for? SOC 2, an attestation report against the Trust Services Criteria FedRAMP, an authorization for US federal cloud services ISO 27001, the international standard for certifying an ISMS NIST CSF, a voluntary framework for describing cyber risk
Question 2 of 20 · GRC Engineering Foundations A team snapshots live cloud configuration every hour, signs each snapshot, and alerts on drift within minutes. Every change to production is still made by hand in the console by an engineer following a runbook. Which of the three pillars is missing? Automate, because the controls live in a runbook and not in code Evidence, because hourly snapshots are not machine verifiable Continuous, because drift alerts only fire after a change is made Translation, because the runbook is written only for engineers
Question 3 of 20 · GRC Engineering Foundations A program sits solidly at Automated (Level 3) on the GRC Engineering Maturity Model. Which change best represents the step up to Continuous (Level 4)? Assigning a named owner to each policy and listing controls in a tracker Moving storage and IAM configuration into reviewed Terraform modules Letting the system tune its own rules and heal its own controls Treating each merge as an audit event, with live telemetry on dashboards
Question 4 of 20 · Infrastructure as Code What does a default_tags block inside the Terraform AWS provider configuration do for a CM-6 required-tags control? It fails the plan whenever a resource block omits a required tag It applies the listed tags to every taggable resource it manages It copies tags from the state bucket onto each newly created resource It adds the listed tags only to resources declared inside child modules
Question 5 of 20 · Infrastructure as Code A compliance module declares this input: variable "environment" { type = string validation { condition = contains(["dev", "staging", "prod"], var.environment) error_message = "environment must be dev, staging, or prod." } }. A consumer calls the module with environment = "sandbox" and runs terraform plan. What happens? The plan succeeds and Terraform prints the message as a warning The plan succeeds and the value silently falls back to "dev" The plan succeeds, then apply stops after the first resource The plan fails with the error message before anything is changed
Question 6 of 20 · Infrastructure as Code You are designing an S3 evidence vault. The requirement says no one, including an account administrator, may delete or overwrite an evidence object or shorten its retention for three years. Which Object Lock setting meets it? COMPLIANCE mode with a three year default retention period GOVERNANCE mode with a three year default retention period Versioning enabled with a three year lifecycle expiration rule A bucket policy that denies s3:DeleteObject to all principals
Question 7 of 20 · Infrastructure as Code Two engineers trigger terraform apply against the same workspace at nearly the same moment. The workspace uses a remote backend with state locking enabled. What should the second run do? Merge its changes into the first run's state when both finish Overwrite the first run's state, since the last writer wins Stop with a state lock error because it cannot acquire the lock Create a second state file and reconcile it on the next plan
Question 8 of 20 · Policy-as-Code A Rego unit test contains this line: count(deny) == 1 with input as unencrypted_bucket_plan. What does the "with input as" clause do when opa test runs? It writes the fixture to disk as plan.json for a later Conftest run It substitutes the fixture as the input document for that one expression It merges the fixture into the data document for all later tests It imports the package that the fixture's rules were written in
Question 9 of 20 · Policy-as-Code Your deny rules live in a file that starts with package terraform.compliance. You run conftest test plan.json --policy ./policies against a plan you know is non-compliant, and Conftest reports no failures. What is the most likely cause? Conftest only evaluates the main namespace unless told otherwise Conftest cannot read Terraform plans that were exported as JSON Conftest ignores deny rules and only evaluates rules named allow Conftest requires every policy to pass opa test before it loads
Question 10 of 20 · Policy-as-Code A blocking policy is live in CI. One team has a legitimate, temporary reason it cannot comply. What should the policy program offer so the team does not simply switch the check off? Admin merge rights so the team can skip the failing check A lower severity on the rule so it no longer blocks anyone A logged and approved exception path with a named owner A commented-out copy of the rule until the project ships
Question 11 of 20 · CI/CD for GRC Engineers You review the trust policy on an AWS role that GitHub Actions assumes through OIDC. It allows sts:AssumeRoleWithWebIdentity from the GitHub OIDC provider and checks only that the audience is sts.amazonaws.com. What is the gap? The role still needs a long-lived access key stored as a repo secret The role can only be assumed from workflows on the default branch The role session cannot upload objects to an Object Lock bucket Workflows in any GitHub repository could assume the role
Question 12 of 20 · CI/CD for GRC Engineers In a compliance workflow, the Conftest step exits non-zero on a violation and the job stops. The upload-artifact step that follows never runs, so blocked pull requests leave no evidence behind. Which change keeps the gate failing closed and still captures evidence? Set continue-on-error: true on the Conftest step Add if: always() to the upload-artifact step Move the upload step ahead of terraform plan Run Conftest with the --no-fail flag in CI
Question 13 of 20 · CI/CD for GRC Engineers In the Cosign keyless signing flow used for evidence bundles, what role does Rekor play? It issues the short-lived signing certificate for the run It records the signing event in a public transparency log It stores the evidence bundle under a retention lock It mints the OIDC identity token for the CI runner
Question 14 of 20 · Cloud-Native Security & Monitoring What does enabling log file validation on an AWS CloudTrail trail add to your audit evidence? Encryption of every log file with a customer managed KMS key Delivery of the same log files to a second AWS region Automatic removal of log files older than the retention period Signed digest files that reveal altered or deleted log files
Question 15 of 20 · Cloud-Native Security & Monitoring An auditor asks who read objects in a sensitive Cloud Storage bucket in a GCP project last month. The team finds Admin Activity entries in Cloud Audit Logs but no record of object reads. What is the most likely explanation? Data Access audit logs are off by default and were never enabled Cloud Audit Logs only keeps entries of any type for seven days Object reads are recorded only in Security Command Center findings Admin Activity logs must be disabled before read logging can start
Question 16 of 20 · Cloud-Native Security & Monitoring A GCP organization enforces the Org Policy constraint iam.disableServiceAccountKeyCreation. A developer with the Owner role on a project tries to create a JSON key for a service account so a GitHub Actions pipeline can deploy. What happens, and what is the right path forward? The key is created, and a posture finding is raised for review later. Rotate it every 90 days. The key is created because Owner overrides Org Policy. Store it as an encrypted repo secret. The create call is rejected at the API. Use Workload Identity Federation for the pipeline. The create call is rejected at the API. Ask an org admin to mint the key and share it.
Question 17 of 20 · OSCAL & Continuous Authorization A teammate hand-writes an OSCAL component-definition.json and sets the component's identifier to "uuid": "s3-module-001" so it is easy to read. trestle validate rejects the file. Why? Component definitions must be authored in YAML, not in JSON A component may only be declared inside a System Security Plan The identifier must match the name of the Terraform module OSCAL uuid fields must hold a properly formatted RFC 4122 UUID
Question 18 of 20 · OSCAL & Continuous Authorization You are writing an OSCAL Component Definition for a Terraform storage module. Where do you record the claim that this component satisfies SC-28, along with a link to the signed evidence? In a new control entry added to the NIST 800-53 Catalog In an implemented-requirement under a control-implementation In the import section of the Profile that selects SC-28 In the metadata title field at the top of the document
Question 19 of 20 · Applied GRC Engineering You are finishing your capstone and one control you planned to cover never got built. The rest of the repo works end to end. What is the best way to handle the missing piece? State it as a known gap in the design document, with your reasoning Add a placeholder policy that always passes so the count looks right List the control in the OSCAL component without any evidence link Leave it out of the write-up so the reviewer focuses on what works
Question 20 of 20 · Applied GRC Engineering A reviewer wants to trace one change through an integrated GRC engineering workflow. Which sequence shows the layers connected correctly? A merge triggers apply, the policy gate checks the applied state, then the plan is signed and stored The evidence bundle is signed first, then the plan is generated, the policy gate runs, and apply follows A pull request triggers plan and the policy gate, a pass allows apply, then the evidence is signed and vaulted A pull request triggers apply, the OSCAL file is validated, then the policy gate runs after the merge completes
Submit answers 0 of 20 answered