Advanced Cloud Computing test (Advanced)

Sample questions

5 sample questions from the Advanced Cloud Computing test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. Which of the following statements best describes the complexity of multi-cloud backup retention policies compared to single-cloud policies?

   1. Multi-cloud backup retention policies are the same in complexity as single-cloud policies because they follow identical processes.
   2. Multi-cloud backup retention policies are simpler than single-cloud policies because they eliminate the need for cross-cloud orchestration.
   3. Multi-cloud backup retention policies are generally more complex than single-cloud policies due to the need to manage data across multiple providers, ensuring consistency, compliance, and recovery across platforms.
   4. Multi-cloud backup retention policies are less complex than single-cloud policies because they allow data to be stored in a single location.

   Answer: C. Multi-cloud backup retention policies are generally more complex than single-cloud policies due to the need to manage data across multiple providers, ensuring consistency, compliance, and recovery across platforms.

   Multi-cloud backup retention policies are more complex because they require managing data across multiple cloud providers, ensuring consistency, compliance, and recovery across platforms. This complexity arises from differences in cloud provider tools, data replication strategies, and the need for cross-cloud orchestration. Single-cloud backup policies are simpler because they operate within a single provider's ecosystem.

2. What behavior does a hybrid cloud API gateway exhibit when handling requests to on-premises APIs?

   1. It blocks all traffic to on-premises APIs unless explicitly configured to allow it.
   2. It automatically encrypts all data passing through the gateway, regardless of the destination.
   3. It routes requests to on-premises APIs based on predefined rules and traffic conditions.
   4. It only supports cloud-based APIs and does not integrate with on-premises APIs.

   Answer: C. It routes requests to on-premises APIs based on predefined rules and traffic conditions.

   A hybrid cloud API gateway is designed to manage traffic between on-premises and cloud-based APIs. It uses predefined rules and traffic conditions to route requests efficiently, ensuring that the correct service is accessed based on the request's context, such as API endpoint, user location, or traffic load. This behavior is a core function of an API gateway in a hybrid cloud environment.

3. Which of the following is a recommended cloud cost optimisation strategy for handling workloads with spiky or unpredictable usage patterns?

   1. Run stateful critical jobs on spot instances without checkpointing
   2. Use managed/serverless for spiky workloads
   3. Purchase long-term commitments before rightsizing
   4. Ignore data egress costs for cross-region traffic

   Answer: B. Use managed/serverless for spiky workloads

   Cloud cost optimisation strategies recommend using managed or serverless services for workloads with unpredictable or spiky usage patterns. This is because serverless and managed services automatically scale to handle demand without requiring the user to provision or manage infrastructure, which can lead to cost savings. The other options are either unrelated or not directly aligned with the principle of optimising costs for spiky workloads.

4. A company is implementing a multi-cloud strategy and is encountering issues with inconsistent resource management and governance across different cloud providers. Which of the following actions would best address this issue and ensure interoperability?

   1. Deploy identical virtual machines across all cloud providers without any modifications.
   2. Use Terraform/OpenTofu with provider-specific resources and ensure consistent tagging and policy-as-code.
   3. Rely solely on native tools of each cloud provider for deployment and management.
   4. Ignore tagging and policy-as-code to speed up deployment across clouds.

   Answer: B. Use Terraform/OpenTofu with provider-specific resources and ensure consistent tagging and policy-as-code.

   Terraform/OpenTofu supports multi-cloud environments by using provider-specific resources, which allows for consistent infrastructure deployment across different cloud providers. Consistent tagging and policy-as-code help maintain uniformity and governance across clouds. The other options do not address the core issue of ensuring interoperability and uniform governance across multiple cloud providers.

5. A company is experiencing inconsistencies in API behavior across multiple cloud providers. Which approach should they take to ensure API consistency and avoid duplication of skills and tooling across clouds?

   1. Use Terraform/OpenTofu with provider-specific resources and ensure consistent tagging and policy-as-code across clouds.
   2. Ignore provider-specific differences and assume all APIs are the same.
   3. Deploy identical infrastructure in each cloud without using any portability tools.
   4. Use a single cloud provider's API for all resources and avoid multi-cloud deployments.

   Answer: A. Use Terraform/OpenTofu with provider-specific resources and ensure consistent tagging and policy-as-code across clouds.

   Multi-cloud API consistency is achieved by using portability layers like Terraform/OpenTofu, which abstract provider-specific differences. Consistent tagging and policy-as-code ensure uniformity across clouds. Using provider-specific resources without abstraction can lead to inconsistencies and increased complexity.