NIFCLOUD Fundamentals and Service Overview
What this domain covers
The fundamentals domain tests whether you can place NIFCLOUD in the right service category and reason about scope. NIFCLOUD is Fujitsu's public cloud, delivered through a console and APIs. Resources are created in a region and, for many compute and storage services, in a zone inside that region. A region is a geographic boundary; a zone is an isolation domain for failure. Design for multi-zone only when the service and your latency budget allow it.
Core rules
- Service families map to exam questions: Compute (virtual servers, bare metal, images), Storage (block, object, archive), Networking (private LAN, load balancer, DNS, VPN), Security/IAM, and Operations/billing.
- The provider secures facilities, hardware, and the hypervisor. You secure guest OS patching, application code, identities, data classification, and network rules.
- Resource scope matters: a block volume is tied to a zone; object storage is accessed over the network and is not a boot disk.
- Choose a service by protocol and access pattern, not by name: block for mounted filesystems, object for HTTP APIs, archive for rare retrieval.
- Use the API/CLI for repeatability; console clicks are hard to audit.
Worked example
A web team needs a database and static assets. Put two web virtual servers in different zones behind a load balancer; keep the database on block storage in one zone with backups; put images in object storage. Reasoning: zone separation removes a single failure domain for the web tier; block storage gives low-latency filesystem semantics for the database; object storage serves static content without attaching disks.
Traps
Treating a region as a zone; assuming every service is zone-redundant; forgetting the shared-responsibility split; choosing archive storage for a boot disk; and leaving resources untagged so billing cannot be attributed.