You are maintaining an application that uses the Azure Content Delivery Network (CDN) to serve terabytes of
content that is stored in page blobs.
Your bill for CDN services is higher than you expect.
You need to monitor the application to find issues that increase costs.
Which two operations should you monitor? Each correct answer presents part of the solution.
A.
The Time-To-Live (TTL) of the blobs.
B.
The country of origin for the client computerand the CDN region.
C.
The number of requests that result in an HTTP status code over 400.
D.
The allocated size of page blobs.
E.
The expiration date of the blobs.
B-D
i’d say A and D
Mohamed is correct.
Answer is A, D
https://azure.microsoft.com/en-us/blog/understanding-windows-azure-cdn-billing/
I disagree I think it should be A and E.
If the expiration the blobs is too short then more request have to be made from CDN to Storage. This will increase the Network Outbound costs.
https://azure.microsoft.com/en-gb/documentation/articles/cdn-manage-expiration-of-blob-content/
Then what is a “The expiration date of the blobs.”? There is no such thing, just TTL.
It’s A and B
https://azure.microsoft.com/en-us/pricing/details/cdn/
Think i found the answer: Set the longest TTL possible on your content – from https://msdn.microsoft.com/en-us/library/azure/dn194239.aspx>
Believe answer is A and B
B is not involved in the cost, see also:
https://azure.microsoft.com/en-us/blog/understanding-windows-azure-cdn-billing
I think it should be A and C
Agree with Rockfly -> A and C
https://azure.microsoft.com/en-us/blog/understanding-windows-azure-cdn-billing
We came across a cool site that you simply may well enjoy. Take a look in the event you want.
I think it should be B and C
A-D
For A: From MS: Each time a CDN point of presence needs to fill its cache, it will make a request to the origin for the object being cached. This means the origin will incur a billable transaction on every cache miss. How many cache misses you have depends on a number of factors:
How “cacheable” content is: If content has high TTL/expiration values and is accessed frequently so it stays popular in cache, then the vast majority of the load is handled by the CDN. A typical “good” cache-hit ratio is well over 90%, meaning that less than 10% of client requests have to return to origin (either for a cache miss or object refresh).
How many nodes need to load the object: Each time a node loads an object from the origin, it incurs a billable transaction. This means that more global content (accessed from more nodes) results in more billable transactions
Influence of TTL: A higher TTL (Time-To-Live) for an object means it needs to be fetched from the origin less frequently. It also means clients (like browsers) can cache the object longer, which can even reduce the transactions to the CDN.
B: NOT because : The CDN billing region is based on the location of the source server delivering the content to the end user. The destination (physical location) of the client is not considered the billing region.
C: NOT because : For example, 304 NOT MODIFIED (and other header-only) responses generate very little transfer since they are a small header response; similarly, error responses (e.g., 404 NOT FOUND) are billable but incur very little cost because of the tiny response payload.
D: If you are using blob storage as “origin” for your content, you also incur charges for cache fills for:
Storage – actual GB used (the actual storage of your source objects),
Storage – transfer in GB (amount of data transferred to fill the CDN caches), and
Storage – transactions (as needed to fill the cache. Read this blog post for more information.)
E: expiration date dont know what it is looks same like TTL
Actual GB used so (Allocated size of page blobs is not billed) D is wrong damn.
i will use A-C
The answer looks correct. See link below for more details:
https://azure.microsoft.com/en-us/blog/understanding-windows-azure-cdn-billing/