Download Google.Professional-Cloud-Architect.Dump4Pass.2024-11-26.245q.tqb

Note: The principle of least privilege and separation of duties are concepts that, although semantically different, are intrinsically related from the standpoint of security. The intent behind both is to prevent people from having higher privilege levels than they actually need  Principle of Least Privilege: Users should only have the least amount of privileges required to perform their job and no more. This reduces authorization exploitation by limiting access to resources such as targets, jobs, or monitoring templates for which they are not authorized. Separation of Duties: Beyond limiting user privilege level, you also limit user duties, or the specific jobs they can perform. No user should be given responsibility for more than one related function. This limits the ability of a user to perform a malicious action and then cover up that action.  Reference: https://cloud.google.com/kms/docs/separation-of-duties  

D: Handling "Unable to connect on port 22" error message Possible causes include:  There is no firewall rule allowing SSH access on the port. SSH access on port 22 is enabled on all Compute Engine instances by default. If you have disabled access, SSH from the Browser will not work. If you run sshd on a port other than 22, you need to enable the access to that port with a custom firewall rule. The firewall rule allowing SSH access is enabled, but is not configured to allow connections from GCP Console services. Source IP addresses for browser-based SSH sessions are dynamically allocated by GCP Console and can vary from session to session.  F: Handling "Could not connect, retrying..." error You can verify that the daemon is running by navigating to the serial console output page and looking for output lines prefixed with the accounts-from-metadata: string. If you are using a standard image but you do not see these output prefixes in the serial console output, the daemon might be stopped. Reboot the instance to restart the daemon.  Reference: https://cloud.google.com/compute/docs/ssh-in-browser https://cloud.google.com/compute/docs/ssh-in-browser  

From scenario: Business Requirements include: Expand services into Asia Technical Requirements include: Decrease latency in Asia 

Common workloads for Google Cloud Datastore:  User profiles Product catalogs Game state  Reference: https://cloud.google.com/storage-options/ https://cloud.google.com/datastore/docs/concepts/overview  

From scenario: Requirements for Game Backend Platform  Dynamically scale up or down based on game activity Connect to a managed NoSQL database service Run customize Linux distro  

503 is service unavailable error. If the database was online everyone would get the 503 error.  

Ingest millions of streaming events per second from anywhere in the world with Cloud Pub/Sub, powered by Google's unique, high-speed private network. Process the streams with Cloud Dataflow to ensure reliable, exactly-once, low-latency data transformation. Stream the transformed data into BigQuery, the cloud-native data warehousing service, for immediate analysis via SQL or popular visualization tools. From scenario: They plan to deploy the game’s backend on Google Compute Engine so they can capture streaming metrics, run intensive analytics. Requirements for Game Analytics Platform Dynamically scale up or down based on game activityProcess incoming data on the fly directly from the game serversProcess data that arrives late because of slow mobile networksAllow SQL queries to access at least 10 TB of historical dataProcess files that are regularly uploaded by users’ mobile devicesUse only fully managed servicesReference: https://cloud.google.com/solutions/big-data/stream-analytics/ 

Reference: https://cloud.google.com/storage/docs/gsutil/commands/cp