pdf

InformationWeek - Don't Get Burned 4 Steps To A Cloud SLA.pdf
Informationweek Don't Get Burned 4 Steps To A Cloud Sla

Article providing guidance on negotiating effective Service Level Agreements for cloud services.

This page contains AI generated content. Errors or omissions may be present. Use human level critical thinking.
  • Q: What is the 'black box' cloud model?
    A: A model where customers implicitly give up the right to direct how and when most tasks are performed.
  • Q: What is the remedy for the stress of the 'black box' model?
    A: Robust service-level agreements (SLAs) tailored to the as-a-service paradigm.
  • Q: What should be included alongside an SLA?
    A: A service specifications document spelling out respective responsibilities.
  • Q: What should you avoid in SLA remedies?
    A: Limitations on further remedies, such as consequential damages or the option to terminate without liability.
  • Q: Why should you avoid 'Performance credits are the sole remedy' clauses?
    A: Because they limit your right to pursue additional damages in cases of gross negligence.
  • Q: What is the recommended credit percentage for missed SLAs?
    A: 15% credit payment is a typical calibration for a total of 100 points.
  • Q: What should be defined regarding data removal?
    A: The customer's ability to remove data from the cloud and the mechanisms for doing so.
  • Q: What is a 'Service Level Objective' vs. SLA?
    A: An objective is a target; an SLA is a contract with penalties.
  • Q: Who is the author of this article?
    A: Jonathan Shaw, a principal at Pace Harmon.
  • Q: What date was this article published?
    A: 9/28/2011.

Ask a question

Have a doubt or need clarification?



I’m here to help. Share your question, and I’ll get back to you with the guidance you need regarding the course.

Thank you!

I have received your message and I shall get back to you shortly.