Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Linux Foundation KCNA Exam - Topic 3 Question 75 Discussion

Actual exam question for Linux Foundation's KCNA exam
Question #: 75
Topic #: 3
[All KCNA Questions]

Which of the following is a challenge derived from running cloud native applications?

Show Suggested Answer Hide Answer
Suggested Answer: B

The correct answer is B. Cloud-native applications often run across multiple environments---different cloud providers, regions, accounts/projects, and sometimes hybrid deployments. This introduces real cost-management complexity: pricing models differ (compute types, storage tiers, network egress), discount mechanisms vary (reserved capacity, savings plans), and telemetry/charge attribution can be inconsistent. When you add Kubernetes, the abstraction layer can further obscure cost drivers because costs are incurred at the infrastructure level (nodes, disks, load balancers) while consumption happens at the workload level (namespaces, Pods, services).

Option A is less relevant because cloud-native adoption often reduces dependence on maintaining a private datacenter; many organizations adopt cloud-native specifically to avoid datacenter CapEx/ops overhead. Option C is generally untrue---public registries and vendor registries contain vast numbers of images; the challenge is more about provenance, security, and supply chain than ''lack of images.'' Option D is incorrect because major clouds offer abundant services; the difficulty is choosing among them and controlling cost/complexity, not a lack of services.

Cost optimization being complex is a recognized challenge because cloud-native architectures include microservices sprawl, autoscaling, ephemeral environments, and pay-per-use dependencies (managed databases, message queues, observability). Small misconfigurations can cause big bills: noisy logs, over-requested resources, unbounded HPA scaling, and egress-heavy architectures. That's why practices like FinOps, tagging/labeling for allocation, and automated guardrails are emphasized.

So the best answer describing a real, common cloud-native challenge is B.

=========


Contribute your Thoughts:

0/2000 characters
Antonio
1 day ago
B is definitely a big issue for many companies.
upvoted 0 times
...
Jackie
22 days ago
D seems off too; major clouds usually have a wide range of services, but I guess it depends on what you need for your app.
upvoted 0 times
...
Isabella
27 days ago
I think C is a bit misleading; there are plenty of container images available, but maybe they aren't all suitable for every use case?
upvoted 0 times
...
Aileen
1 month ago
I’m not entirely sure, but I feel like A is less relevant since cloud native apps don’t rely on on-prem data centers as much.
upvoted 0 times
...
Alyssa
1 month ago
I remember discussing how cost optimization can be tricky with multi-cloud strategies, so I think B might be the right choice.
upvoted 0 times
...

Save Cancel