Skip to main content

Secure Access for Cloud Architects

Secure access in cloud architecture is designing who and what may reach resources. It covers identity design with roles, federation and multi-factor authentication, network boundaries and private connectivity, and protecting workloads and data through encryption at rest and in transit, key management and secrets handling.

Stage: Secure Architectures · Part of the Cloud Architect roadmap · Last reviewed 19 November 2026

What to learn in Secure Access

Secure Access interview questions

Why prefer roles with temporary credentials over long-lived access keys?

Temporary credentials expire automatically, so a leak has a limited window and there is nothing permanent to rotate or hide in code. Roles also tie access to a workload identity, making permissions easier to audit and scope narrowly.

What is the shared responsibility model?

The provider secures the underlying infrastructure, while the customer secures what they put on it, such as identity settings, data, network rules and application code. The exact split depends on the service type, from virtual machines to managed platforms.

Where Secure Access fits in the Cloud Architect roadmap

Secure Access belongs to the Secure Architectures stage (advanced level), which takes about 38 hours. Protect workloads and data.

Back to the full Cloud Architect roadmap