Intermediate Cloud Computing test (Intermediate)

Sample questions

5 sample questions from the Intermediate 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. A cloud engineer notices that their auto-scaling group is frequently adding and removing instances in response to minor fluctuations in traffic. What is the most likely cause of this issue?

   1. The cooldown period is appropriately set, but the scaling policies are misconfigured.
   2. The cooldown period is not relevant to the current issue, and the problem lies elsewhere.
   3. The cooldown period is too short, leading to frequent scaling actions and instability in the environment.
   4. The cooldown period is too long, causing delays in scaling actions and inefficient resource utilization.

   Answer: C. The cooldown period is too short, leading to frequent scaling actions and instability in the environment.

   A short cooldown period can cause the auto-scaling group to react too quickly to temporary fluctuations in load, leading to unnecessary scaling actions and instability. A longer cooldown period allows the system to stabilize before making scaling decisions, ensuring that the environment remains stable and efficient.

2. Which of the following statements accurately describes private endpoints compared to public endpoints in cloud computing?

   1. Private endpoints are only available in certain regions and are generally more complex to set up.
   2. Private endpoints are more secure and reduce exposure to the internet, but may require additional configuration for connectivity.
   3. Private endpoints require no configuration and are always more performant than public endpoints.
   4. Private endpoints are less secure than public endpoints but are easier to configure.

   Answer: B. Private endpoints are more secure and reduce exposure to the internet, but may require additional configuration for connectivity.

   Private endpoints provide secure, direct connectivity to services within a VPC without exposing them to the internet, which enhances security. However, they require proper routing and network configuration. Public endpoints are accessible over the internet but expose services to potential threats. Private endpoints are not inherently more complex than public endpoints; complexity depends on the specific use case and network setup. They also do not require additional network infrastructure compared to public endpoints, as they are managed by the cloud provider.

3. Your team is deploying a multi-VPC architecture where two VPCs need to communicate with each other through VPC peering. What must be done to ensure that route propagation works correctly between the two VPCs?

   1. The route tables in both VPCs must have routes pointing to each other's VPC peering connections.
   2. VPC peering connections automatically propagate routes without manual configuration.
   3. Only the route table in the primary VPC needs to be updated with the peering connection route.
   4. Route propagation is handled entirely by the cloud provider and does not require any configuration.

   Answer: A. The route tables in both VPCs must have routes pointing to each other's VPC peering connections.

   When two VPCs are peered, route propagation must be explicitly configured in the route tables of both VPCs to ensure traffic can flow between them. This is a critical step in establishing connectivity between peered VPCs. Other options are either incorrect or not directly related to route propagation.

4. A developer is experiencing connectivity issues between two VPCs that are peered. They have confirmed that the VPC peering connection is established and the subnets are using non-overlapping CIDR ranges. What is the most likely cause of the issue?

   1. The route tables in the VPC are not associated with the correct subnets.
   2. The route propagation is not configured correctly in the VPC route table.
   3. The subnets in the VPC are using overlapping CIDR ranges.
   4. The VPC peering connection is not established between the two VPCs.

   Answer: B. The route propagation is not configured correctly in the VPC route table.

   Route propagation is the process of sharing routes between VPCs that are connected via VPC peering. If the route propagation is not configured correctly in the VPC route table, it can prevent traffic from being routed properly between the peered VPCs. This is a common issue when setting up VPC peering and can lead to connectivity problems between resources in the peered VPCs.

5. A cloud-native application is failing to display logs in the centralized logging service. What is the most likely cause of this issue?

   1. The application's dependencies are not being installed correctly.
   2. The application's code is not being built correctly.
   3. The application's configuration files are not being deployed correctly.
   4. The application's logs are not being collected or forwarded correctly to the centralized logging service.

   Answer: D. The application's logs are not being collected or forwarded correctly to the centralized logging service.

   In a cloud-native CI/CD pipeline, logs are typically collected from containers or serverless functions and forwarded to a centralized logging service for monitoring and debugging. If the logs are not being collected or forwarded correctly, it can be a bug in the CI/CD pipeline's logging configuration or integration with the logging service. This is a common issue in cloud-native applications and can be fixed by ensuring the logging configuration is properly set up and tested.