C. Export the billing data to BigQuery. Create a Cloud Function that uses BigQuery to sum the egress network costs of the exported billing data for the Apache web server for the current month and sends an email if it is over 100 dollars. Schedule the Cloud Function using Cloud Scheduler to run hourly.

[C] I think the keyword here is "as measured by Google Cloud". In Answer D you calculate the price yourself, in C you use the billing provided by GCP. Thus I think the Answer is C.

I would never had guessed C or D. I thought it's A, as it's the most straight forward. C or D are ridiculously complex to me.

Correct answer is C.

C is the correct answer , as it gives you everything the question wants

Answer is A From this Link: https://cloud.google.com/load-balancing/docs/ssl it states this: External SSL proxy load balancers are intended for non-HTTP(S) traffic. For HTTP(S) traffic, we recommend that you use an external HTTP(S) load balancer. 443 is HTTPS traffic for those saying 443 isn't https https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=443

Took the exam this week this question is on there, C is the correct answer you need to remember to filter.

C is the correct answer, You export the bill to BigQuery and filter for the Egress cost for the particular application, and send an email if the cost is over 100 dollars, to send an email you need to use cloud function to monitor and trigger based on the conditions.

it can only be the C because "it's not the only app running"

[D] Complex but works for resume network egres cost of ONLY the Apache instance

I would say this is the approach without knowing that much: A & B discarded as they are not resourced oriented. We need to charge for the apache server (so focusing on the VM where it is hosted) in order to charge this server. D can't be as you are not charged in this case for that Response payload received.

Answer C and D are correct to me. You can calculate the current Google Cloud egress prices using Cloud billing catalog API which can be used in D option. ref: https://cloud.google.com/blog/topics/cost-management/introducing-cloud-billing-catalog-api-gcp-pricing-in-real-time But, if you choose option C, then you will get the usage cost directly from cloud billing data. You should add a label to the Apache web server in order to select its cost. D has the more complex step, using more services too which is Cloud Logging to store the logging data of the VM and Cloud Billing Catalog API. The using of more services makes the D option to have more expensive costs.

C is best options

C is best options

C cannot be the right answer, you export the data to big Query only once. What is the use of a cloud function running every hour on the same data? It doesn't say "you export the data to BigQuery hourly".

I feel the answer should be B as projects can be specified and also services.

It's C