en-US: https://www.microsoft.com/en-us/server-cloud/solutions/hybrid-cloud.aspx
ko-KR: https://www.microsoft.com/ko-kr/server-cloud/solutions/hybrid-cloud.aspx
Literal translation doesn’t deliver the meaning.
Source: Why choose between your datacenter and the cloud? A hybrid cloud solution gives you both.
Target; 왜 데이터센터와 클라우드 중에서 선택해야 합니까? hybrid cloud 솔루션이 두 가지 기능을 모두 제공합니다.
-> “why” sentence reads literal wording, which makes the tone awkward. It was supposed to be in a suggestive tone. “Hybrid Cloud” reads two different spells. The first letter in body text even shows non-capitalized.
Source: Connect hosting provider and tenant networks for hybrid cloud services
Target: 하이브리드 클라우드 서비스를 호스팅 제공 업체와 세입자의 네트워크를 연결
-> “tenant network” reads a dictionary term along with a possessive noun ending so it doesn’t fit in context.
Source: Your business requires a flexible IT infrastructure that can scale on demand.
Target: 귀사에서는 필요 시 확장 가능한 유연한 IT 인프라가 필요합니다.
-> Another awkward word-for-word translation.
Source: With a private cloud in your datacenter, you can be more agile and manage resources more effectively. When you extend your datacenter to meet the public cloud, you are working in a hybrid cloud model.
Target: 데이터센터의 private cloud를 통해 민첩성을 높이고 리소스를 보다 효율적으로 관리할 수 있습니다. 데이터센터를 public cloud에 맞게 확장하여 hybrid cloud 모델에서 작업합니다.
-> Inconsistent terms “private cloud” and “public cloud.” The terms read different spells “사설 클라우드” and “공용 클라우드.” This is a critical issue.
Source: Extending into the cloud should expand your options without adding complexity.
Target: 클라우드로 확장하면 복잡성을 추가하지 않으면서 옵션을 확장할 수 있습니다.
-> Another awkward word-for-word translation “without adding complexity”
