Course Test

Question 1

A Meshery design differs from a plain Kubernetes manifest primarily because it:

Select one answer

Uses a proprietary binary format that is smaller than YAML

Can only be deployed via the Meshery UI, not the CLI

Carries relationship declarations between components that enable validation and topology rendering

Requires a Meshery Operator to be installed before it can be stored

Question 2

After running `mesheryctl design import -f designs/microservices-demo.yaml -s "Kubernetes Manifest"`, what does Meshery return on success?

Select one answer

A Kanvas URL where the design can be viewed immediately

A confirmation message and the design ID (UUID)

A diff showing what changed relative to the current cluster state

An OPA policy report listing any policy violations in the manifest

Question 3

Which of the following actions are part of the recommended pull-request preview workflow for GitHub-backed designs?

Select all that apply

A CI job imports the modified design into a staging Meshery instance when a PR is opened

A Kanvas snapshot of the topology is posted as a PR comment for reviewer inspection

The design is automatically deployed to production as soon as the PR is opened

A platform engineer reviews the visual topology diff and YAML diff before approving

Question 4

In Meshery's RBAC model, which built-in workspace role is appropriate for a CI pipeline or coding agent that only needs to create and modify designs in a non-production workspace?

Select one answer

Admin

Viewer

Editor

Deployer

Question 5

What is the purpose of the `-s "Kubernetes Manifest"` flag in the `mesheryctl design import` command?

Select one answer

It sets the storage backend where the design will be saved

It specifies the source schema Meshery uses to parse and map the file's contents to registered components

It selects the Kubernetes namespace the design will be deployed into

It authenticates the import operation against the Meshery server

Question 6

Which of the following correctly describes the relationship between environments and workspaces in Meshery?

Select one answer

An environment contains one or more workspaces; each workspace maps to a single cluster

Workspaces and environments are the same concept, just named differently in different versions of Meshery

A workspace is the access-control container that groups environments, designs, and members; environments are the deployment targets within a workspace

Environments are created automatically when a workspace is created and cannot be managed independently