Cloud Security Architect

Sample question 1

Harrow Defense Systems is building a sensor fusion platform for a coalition unit. The platform must ingest Top Secret intelligence feeds and Secret level tactical sensor data, then produce a single Secret level common operating picture for field commanders who hold only Secret clearances. The design must guarantee that no Top Secret content is ever exposed in that downstream picture. As the cloud security architect, which design approach correctly satisfies this multilevel requirement?

1. A.Run the fusion platform as one system at the Top Secret watermark and rely on attribute based access control to filter Top Secret content whenever a Secret cleared user queries the common operating picture.
2. B.Route the Top Secret to Secret data flow through a cross domain guard that performs automated content inspection and human reviewed sanitization before any output reaches the Secret picture, blocking anything that fails review.
3. C.Place the two feeds on separate network segments joined by a firewall permitting only Secret to Top Secret traffic, and have analysts manually retype any needed Top Secret detail into the Secret picture.
4. D.Encrypt the Top Secret feed in transit into the fusion platform, store it apart from the Secret data, and publish only automatically generated aggregate statistics into the Secret common operating picture.

Sample question 2

During an AI system audit at a healthcare analytics firm, the cloud security architect finds that the same small team of data scientists can, all under one shared service account credential, pull identifiable patient records into the training data store, fine-tune the clinical-notes summarization model, and approve the updated model for production. Which finding should the architect prioritize in the risk report?

1. A.The model's summarization outputs are stored without encryption at rest, which could let an attacker who gains network-level access to the storage layer read identifiable clinical notes directly.
2. B.The training data store's password policy does not enforce the firm's standard minimum length of 14 characters, though multi-factor authentication is still required for every login attempt.
3. C.The environment lacks segregation of duties: one shared credential lets the same people create training data, fine-tune the model, and approve its own deployment, with no individual accountability.
4. D.The shared service account has a session timeout of eight hours rather than the 30-minute idle timeout the firm applies to interactive human user accounts on other systems.

Sample question 3

You are the Cloud Security Architect at a manufacturing company modernizing its factory-floor monitoring platform. The DevOps team proposes a single service identity for the deployment pipeline: it can merge pull requests into the main branch, run the Terraform plan and apply steps, and hold the long-lived cloud credentials that create and modify production resources, all so one integration reduces pipeline complexity. Applying access control principles, what is the strongest objection you should raise before approving this design?

1. A.The strongest objection is that the identity would be over-privileged, carrying broad standing rights to create and modify production resources far beyond any single step, so the design violates least privilege, and scoping its permissions down to only the specific Terraform resources this pipeline manages is what applying separation of duties to this design requires before approval.
2. B.The strongest objection is that the identity would depend on long-lived cloud credentials, so a single theft would grant lasting access, and the separation of duties this design lacks is restored once those credentials are replaced with short-lived tokens issued fresh and rotated automatically before each individual pipeline run, which keeps any stolen credential from being reused across deployments.
3. C.The strongest objection is that one identity would hold both the authority to merge a change into the main branch and the authority to apply it to production; those two functions must sit with separate identities, because otherwise a single compromise of the pipeline identity, including through the build runner, could push an unreviewed change straight into production.
4. D.The strongest objection is that separation of duties is absent at the merge step, so requiring a second independent reviewer to approve each pull request before it merges supplies that separation between author and approver, which addresses the concern right at the point where new changes actually enter the main branch that the deployment pipeline consumes.