Google Google Adword Reporting and Analysis Exam Prep
Google Adword Reporting and Analysis (Page 7 )

• When the MVP will be defined — the MVP should already be understood sufficiently when assessing the business case.
• What the MVP is — useful information, but not the key requirement tested here.
• That the MVP is the same as project viability — incorrect. The MVP helps test viability; it is not identical to viability itself.

• Response and resolution time frames
• Availability or uptime requirements
• Performance targets
• Support obligations
• Penalties for failing to meet requirements

• SOW (Statement of Work): Defines the project’s scope, tasks, and deliverables.
• MOA (Memorandum of Agreement): Describes cooperation and responsibilities between parties.
• MOU (Memorandum of Understanding): Records a general mutual understanding, usually without detailed enforceable service targets.

• IaaS: You deploy and manage virtual machines, including the operating system and installed software. Azure manages the physical datacenter, hosts, and networking infrastructure.
• PaaS: Azure manages the infrastructure and operating system, while you deploy and manage your application code. Examples include Azure App Service and Azure Functions.

• A is valid:

apex 
  for (Account theAccount : AccountList) { 
      // process theAccount 
  }

• D is conceptually valid, using an index:

apex 
  for (Integer i = 0; i < AccountList.size(); i++) { 
      Account theAccount = AccountList[i]; 
  }

• B is invalid because for(AccountList) is not valid loop syntax.
• C is invalid because each item is an Account, not a List.

• A — .gitignore: Controls Git tracking; it does not configure Copilot exclusions.
• B — copilot.ignore: This is not the standard GitHub Copilot Business exclusion mechanism.
• D — Renaming files: Adding _no_copilot has no recognized effect.

• A business-hours greeting
• An after-hours greeting
• A holiday greeting

• Weekday evenings/nights
• Saturdays and Sundays

1. Auto attendant 1

1. Auto attendant 2

• Azure Cosmos DB is a globally distributed NoSQL database service. It stores and retrieves application data, but it does not provide the complete environment for building, testing, and deploying predictive analytics models.
• Azure Machine Learning is the appropriate service for this requirement. It supports creating experiments, training and testing models, and deploying them for predictions.
• Azure Machine Learning Studio provides the browser-based interface for these tasks.

• Initial Intrusion: The compromised VPN account and stolen phishing credentials describe how the attacker first gained access, but that happened months earlier.
• Persistence: The scheduled tasks and recurring C2 connections show how the attacker maintained and automated continued access.
• Search and Exfiltration: This would involve locating and transferring data. The scenario does not primarily describe data discovery or theft.
• Cleanup: Cleanup involves removing evidence or covering tracks. Obfuscated scripts may make detection harder, but the main behavior here is maintaining access.

• netstat -tuln can show listening TCP ports.
• If the web service is not listening, or is bound only to 127.0.0.1, remote browsers cannot connect even though the server responds to ping.

• traceroute: Tests the path to the server, but ping already confirms basic reachability.
• tcpdump: Useful for detailed packet analysis, but it is more appropriate after checking whether a service is listening.
• arp: Helps troubleshoot local IP-to-MAC resolution, not an application-layer web connection.

1. Clear principles and boundaries — Employees have freedom, but decisions must remain within clear organizational values, policies and limits.
2. High degree of freedom — Managers are trusted to make decisions rather than seeking continual approval from senior management.
3. Frontline customer responsibility — Customer-facing managers should be empowered to manage customer relationships and respond quickly to needs.
4. Transparent and ethical information — Information should be openly available and used honestly, supporting trust and informed decision-making.

• JDBC
• SnowSQL
• Snowflake Web Interface (UI)
• ODBC
• Python connector

• Repetitive and time-consuming
• Based on measurable conditions, such as last check-in time
• Easy to automate with alerts, dashboards, or scheduled reports
• Important for ensuring scan coverage

• Assigning custom recommendations usually requires analyst judgment and context.
• Analyzing false positives can sometimes be assisted by automation, but validation often requires human review.
• Rendering an additional executive report increases reporting activity rather than reducing a core operational workload.

• Accept terms of use
• Enter a temporary code or credentials
• Provide basic registration information

• Enterprise authentication — Authenticates organizational users, often with centralized identity services; it is not specifically designed for temporary guest access.
• Ad hoc network — A temporary device-to-device network, not an authentication process.
• WPA3 — A wireless security standard. It protects Wi-Fi access but does not provide the web-based temporary access workflow described here.

• C. Case after-insert trigger that publishes a Platform Event

• D. Custom Apex controller that publishes a Platform Event

• A. Trigger with a callout: Salesforce triggers should not make direct synchronous callouts, and this tightly couples transaction processing to the external system.
• B. Workflow Rule with Outbound Message: This can react to record changes, but it cannot reliably capture a user clicking a menu item. It also does not provide the same flexible event-driven model as Platform Events.

• Training data for potential bias before model training
• Trained models for bias in predictions
• Model features to help explain how they influence predictions

• A: RAG workflows are typically built using services such as Amazon Bedrock, knowledge bases, and data sources.
• B: Monitoring model quality in production is primarily associated with SageMaker Model Monitor.
• C: Documenting model details is handled by capabilities such as SageMaker Model Cards.

• A is correct: It establishes the revised dates and identifies the effect on the critical path.
• B is premature: Stakeholders should be informed after the impact has been assessed and the updated schedule is understood.
• C is not automatically appropriate: Fast-tracking may introduce additional risk and should be considered only after analyzing schedule options.
• D is premature: Adding resources may not resolve a dependency and could increase costs without addressing the actual constraint.

• Labels control access and protection, not blanket exclusion.
• If the user has permission to open a labeled file—especially if the label allows authenticated users to view it—Copilot can use that file in a summary.
• If the label applies encryption and the user lacks the required usage rights, Copilot should not use the file or reveal its contents.
• Copilot honors the user’s existing permissions, so it should not expose labeled content to an unauthorized user.

• The Intune device limit restriction does not apply in the normal way; DEM enrollment supports up to 1,000 devices.
• However, the Microsoft Entra maximum number of devices per user setting can still impose a limit when the enrollment creates an Entra device object.
• Therefore, a DEM account is not automatically unlimited. The effective limit depends on the Entra device setting and the enrollment/join type.

• terraform apply
• terraform destroy

• Sustainability
• Performance efficiency
• Reliability

• An active relationship is used automatically when filters are evaluated. An inactive relationship does not propagate filters unless explicitly activated in DAX, so it would not reliably enforce the required security behavior.
• Apply security filter in both directions allows RLS filters to propagate across the relationship in both directions. This ensures that bidirectional filtering respects the RLS rules applied to both tables.
• Assume referential integrity is unrelated to RLS. It is mainly a DirectQuery optimization that allows Power BI to use an inner join when matching keys are guaranteed to exist.
• The relationship must therefore be active, with security filtering enabled in both directions.

• Honeypots: Deliberately vulnerable or attractive systems designed to lure attackers. Legitimate users should not access them, so activity on a honeypot is a strong indicator of compromise.
• DNS sinkholes: Redirect requests for known malicious domains to a controlled internal system instead of allowing the connection. This can identify infected hosts attempting to contact command-and-control infrastructure.

• Tokenization: Replaces sensitive data with non-sensitive tokens; it protects data but does not primarily detect attackers.
• CI/CD: Automates software development and deployment processes.
• Threat modeling: Identifies potential threats and weaknesses before or during system design.
• Data obfuscation: Makes data harder to understand, but it is not an attacker-detection method.

• The job keeps 31 days of regular restore points. A backup from the week of January 1 is older than 31 days by March 20, so it is no longer expected to remain on the performance tier.
• It is also a weekly GFS full backup, retained for 14 weeks. Therefore, it is still protected and has not been deleted.
• In a Scale-out Backup Repository, older backups can be moved from the performance tier to the capacity tier—typically object storage—according to the configured offload policy.
• The archive tier is not selected because the question’s configuration does not indicate that the backup has been archived there.

• Box 1: No — The rule requires user.department to equal Engineering. Engineer does not match, so User1 is not in AU1. Admin1 cannot reset User1’s password.
• Box 2: No — Admin1’s role is scoped to AU1 and cannot manage users outside that AU.
• Box 3: Yes — Admin2 is a Global Administrator and can reset User3’s password.

• IRR assumes that interim cash flows can be reinvested at the project’s own IRR. This may be unrealistic, especially when the IRR is very high.
• MIRR assumes reinvestment at a specified rate, usually the company’s cost of capital or another realistic reinvestment rate.

• B: MIRR does not specifically favour projects with long payback periods.
• C: MIRR and IRR can rank competing projects differently.
• D: MIRR is not always higher than IRR; it may be higher or lower depending on the cash flows and reinvestment rate.

• Crash cart: Provides local physical access, not remote access.
• Jump box: A secured intermediary used to reach devices over the normal network; it may be inaccessible if the appliance has not booted.
• Secure Shell (SSH): Requires the device’s operating system and network services to be running properly.

• Amazon EC2 instances — ???????? ?? ?? ??????? CPU, memory ??? instance size ???????? ???????
• AWS Lambda functions — memory configuration ?????????? ???????
• Amazon EBS volumes — volume type ?? size optimize ???? ???????
• ??????? ECS workloads — resource configuration ? cost optimization-?? ???????

• Memory ? compute usage ?????????? ???? custom code ????? ???? development ? maintenance ??????
• Cost allocation tags ???? ????? ??? ?????? ???? ??????? ???; inefficient resource ??????? ?? recommendation ???? ???
• CloudTrail resource ???? ?? API activity ??????, resource utilization ????

• Vulnerability scanner: Identifies technical weaknesses in systems, applications, or devices.
• Penetration test: Simulates attacks to determine whether vulnerabilities can be exploited.
• SCAP (Security Content Automation Protocol): Uses standardized formats and protocols for automated vulnerability, configuration, and compliance checks.
• Illumination tool: Maps and analyzes broader supply-chain exposure and third-party risk.

• The type of change: standard, normal, or emergency
• The risk, impact, and complexity
• The change model being used

• A standard change may be pre-authorized through its change model.
• A normal change may require assessment and approval by an appropriate change authority.
• An emergency change may be authorized by an emergency change authority, often using an expedited process.

• Change authorities are not only needed for emergency changes.
• They are not assigned only when a change is deployed.
• They are not only required for normal changes.

1. Search & Intelligence in the Microsoft 365 admin center — No

1. Audit in the Microsoft Defender portal — Yes

1. Audit in the Microsoft Purview portal — Yes

• Maintain head office control: Transfer pricing generally supports decentralisation rather than direct head-office control.
• Establish centralised decision making: This conflicts with divisional autonomy.
• Develop a top-down culture: Transfer pricing is intended to support empowered divisions and goal congruence, not impose purely top-down management.

sql 
ALTER TABLE dbo.DimCustomer 
ADD CONSTRAINT PK_DimCustomer 
PRIMARY KEY NONCLUSTERED (CustomerKey) 
NOT ENFORCED;

1. ALTER TABLE dbo.DimCustomer
2. ADD CONSTRAINT PK_DimCustomer PRIMARY KEY NONCLUSTERED (CustomerKey)
3. NOT ENFORCED

• Treatment one – easier to prepare: Convenience for the accounting team is not the main objective of financial reporting.
• Treatment two – fair representation: This is the correct choice because financial statements must faithfully represent the underlying transaction and its economic substance.
• Treatment three – maximises profit: Accounting policies must not be selected simply to manipulate or inflate reported profit.
• Treatment four – easier to understand: Understandability is important, but it cannot justify presenting information that is less faithfully represented.

• Who owns security risks and decisions
• Who is responsible for implementing controls
• Who reports security performance to management
• How security responsibilities align with business objectives

• B — Compliance with audit requirements: Governance may support compliance, but audit compliance is not its main objective.
• C — Monitoring security incidents: This is an operational security activity, not the central purpose of governance.
• D — Creation of tactical solutions: Governance establishes direction and oversight; tactical solutions belong to management and operational teams.

• Tokens: Individual units of text processed by a model, such as words, subwords, or characters.
• Models: Systems that learn patterns and generate predictions or outputs.
• Binaries: Data represented using the binary number system, not semantic representations.

• Domínios personalizados.
• Armazenamento suficiente.
• Instâncias dedicadas.
• Balanceamento de carga.
• Menor custo entre os planos que atendem a tudo.

• Espionage: Stealing confidential information, often for a competitor or foreign entity.
• Data exfiltration: Unauthorized removal or transfer of data.
• Nation-state attack: A cyberattack sponsored or conducted by a government.
• Shadow IT: Unapproved technology or services used outside IT oversight.

• B — Both inner and outer classes can be declared as with sharing.

• C — Inner classes do not inherit sharing settings from the container class.

apex 
public with sharing class OuterClass { 
    public with sharing class InnerClass { 
        // Explicitly uses sharing rules 
    } 
}

• A static IP gives the surveillance system a predictable local address, so users can reliably reach it on the LAN.
• However, a static IP does not block internet-based login attempts. If the router exposes the device through port forwarding, attackers could still reach it.
• Port mapping normally exposes an internal service externally, so A is a poor choice as written.
• Subnetting alone also does not block traffic; it would require routing/firewall rules.

• Accept: Acknowledging the risk and choosing not to take additional action.
• Transfer: Shifting the risk or financial consequences to another party, such as an insurer.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or access restrictions.
• Avoid: Eliminating the activity that creates the risk.

1. Create a temporary Onboarding OU.
2. Move the new account into it.
3. Move the restrictive SCPs from the organization root to the Production OU.
4. Allow the account to update AWS Config.
5. Move the account into Production after onboarding.

• An SCP attached at the organization root applies to every account and OU beneath it.
• An SCP attached to the Production OU applies only to accounts in that OU.
• Therefore, moving the restrictive SCP from the root to Production temporarily exempts the onboarding account without weakening the policies for existing production accounts.
• Once onboarding is complete, moving the account into Production subjects it to the normal restrictions.

• Two-part tariff pricing: $10 per unit
• Dual pricing: $20 per unit

Two-part tariff pricing

Dual pricing

• Division X, the seller, is credited with the market price: \(\$20\)
• Division Y, the buyer, is charged the marginal cost: \(\$10\)

• Assign endpoints to a group based on the result of one policy.
• Use that group as the scope of another policy.
• This effectively passes the endpoints from one policy’s processing flow to another.

• Minimum
• Maximum
• Average
• Count
• Null/empty values
• Distinct values

• Enable column profile
• Enable details pane
• Show column profile in details pane

1. Open the Microsoft Entra Connect wizard.
2. Select Configure.
3. Choose Customize synchronization options.
4. Authenticate when prompted.
5. On the Domain and OU filtering page, select:

1. Complete the wizard.

• Start-ADSyncSyncCycle only starts synchronization; it does not change which OUs are included.
• Manage federation configures federation settings, which are unrelated to OU filtering.
• Add-ADSyncConnectorAttributeInclusion concerns connector attributes, not selecting additional OUs for synchronization.

• The selling division receives a credit based on a favourable transfer price, often market price or full cost plus a profit margin.
• The receiving division is charged a lower amount, such as marginal cost or another agreed price.
• The difference is accounted for centrally by head office or a corporate adjustment.

• Active-active routers: Provide redundant Internet connections/devices. Both can operate, so traffic can fail over or be load-balanced.
• Active-active firewalls: Avoid a single firewall becoming a failure point while maintaining security inspection.
• Load balancers: Distribute requests across multiple web servers. If one server fails, traffic can go to the other.
• Redundant power supplies: A server with separate power supplies should connect to independent power sources or circuits.
• UPS A and UPS B: Provide backup power and redundancy. Ideally, each power supply is connected to a different UPS.
• SONET ring: A ring topology provides alternate paths if a fiber link or segment fails.

• Three DHCP scopes: Each VLAN has its own IPv4 subnet. DHCP scopes are subnet-specific, so create one scope for:

• Two DHCP relays: DHCP client discovery begins as a broadcast, and broadcasts do not cross routers or VLAN boundaries. Therefore, configure a DHCP relay on the router or Layer 3 switch interface for each client VLAN.

• Additional running costs: $800
• Less depreciation: $300

• The $100 reduction in fixed production overhead absorbed is only an accounting reallocation. It does not represent an actual saving in total fixed overhead.

• New investment: $536,500
• Resulting NPV: $0