正解：

Explanation:
Detailed Explanation
Table storage is supported by the general-purpose Storage (v1) and StorageV2 (general-purpose v2) account kinds, but not by the BlobStorage account kind, which is a specialized, blob-service-only account type introduced before StorageV2 existed. Storageaccount1 (Storage/v1) and storageaccount2 (StorageV2) both support Table storage, while storageaccount3 (BlobStorage) does not -- so ' storageaccount1 and storageaccount2 only ' is correct for the first statement. Blob storage, by contrast, is supported by all three account kinds: general-purpose v1 and v2 accounts include the Blob service alongside Table, Queue, and File, and BlobStorage accounts exist specifically to host block and append blobs. Therefore ' all the storage accounts ' is correct for the second statement. Region (East US vs. Central US) has no bearing on which services a given account kind supports. Both selections match the source document ' s key; no correction is required.
Official Reference
Types of Azure Storage accounts - https://learn.microsoft.com/en-us/azure/storage/common/storage-account- overview

正解：C  🗳️

解説: (Fast2test メンバーにのみ表示されます)

正解：

Explanation:
Detailed Explanation
A blob lifecycle management rule ' s tierToCool action can be triggered by one of three time-based conditions: daysAfterCreationGreaterThan (time since the blob was first created, regardless of later edits), daysAfterLastAccessTimeGreaterThan (time since the blob was last read - only usable if last-access-time tracking is separately enabled on the account), or daysAfterModificationGreaterThan (time since the blob ' s content was last written/updated). " Blobs that were NOT updated for 45 days " specifically describes modification recency, not creation age or read access, so the correct condition is daysAfterModificationGreaterThan, set to 45. For the blob type filter, Azure Blob lifecycle management tiering actions (tierToCool, tierToArchive) apply only to block blobs - page blobs and append blobs are not eligible for automatic tier transitions through lifecycle policy - so the filter should be set to Blockblob (with the existing prefixMatch of " container1 " already scoping the rule to that container).
Official Reference
Optimize costs with blob lifecycle management - https://learn.microsoft.com/en-us/azure/storage/blobs
/lifecycle-management-overview

正解：

Explanation:
Detailed Explanation
A single Recovery Services vault can protect multiple workload types simultaneously - Azure virtual machines and Azure file shares can both be backed up from the same vault, so only one vault is required at minimum; there is no technical requirement here (such as separate regions or separate subscriptions) that would force additional vaults. Backup policies, however, are workload-specific objects: an Azure VM backup policy and an Azure Files backup policy are structurally different resource types with different schedule
/retention schemas, and a single policy cannot be shared across both workload types. Since the scenario needs to protect at least one VM workload and the Azure file shares (container1/share1), the minimum is one VM backup policy plus one Azure Files backup policy - two policies in total. All VMs can share the one VM policy and both file shares can share the one Files policy, since no differing retention/frequency requirement is specified per resource. The correct minimums are 1 vault and 2 policies.
Official Reference
Azure Backup overview - Recovery Services vaults - https://learn.microsoft.com/en-us/azure/backup
/backup-overview