Financial CMA Exam Prep
Certified Management Accountant (Page 46 )

• Define the contractor’s deliverables, responsibilities, acceptance criteria, and deadlines.
• Agree on a reporting cadence to monitor progress.
• Allow the local company to use its expertise and manage its own work.

• A: “Under the supervision of the project manager” suggests excessive direct control and is less empowering.
• B: Micromanaging prevents the contractor from functioning independently and is inefficient.
• D: Deploying the contractor’s staff under the PM’s supervision creates a staffing/control arrangement rather than empowering the contracted company.

• Issuer: Identifies the party issuing a SAML message, commonly the IdP in the SAML assertion. It is not the Salesforce setting used to distinguish Salesforce from other service providers.
• Identity Provider Login URL: Specifies where Salesforce sends users for authentication; it does not identify Salesforce.
• SAML Identity Location: Specifies where the user identity is found in the SAML assertion, such as the subject or an attribute.

1. Download the updated VPN client configuration package from the Azure VPN gateway.
2. Remove or update the existing VPN client configuration on the Windows 10 workstation.
3. Install the new package and reconnect.

• Uses on-premises data or resources
• Runs components in the cloud
• Can scale across multiple cloud environments when demand increases

• Public cloud: Resources are hosted entirely by a cloud provider.
• Private cloud: Resources are dedicated to one organization, usually in its own environment.
• Hybrid: Combines on-premises and cloud resources.

• A limited lifetime
• Permissions defined by an IAM role or policy
• The ability to access AWS APIs without using long-term IAM user credentials

• Amazon API Gateway — Builds and manages APIs; it does not generally issue AWS credentials for applications.
• IAM users — Usually use long-term credentials, which are less suitable for applications.
• IAM instance profiles — Provide temporary role credentials to applications running on EC2 instances, but are specifically tied to EC2. The broader requirement described is best met by AWS STS.

• Idioma: “Responda em português.”
• Tamanho: “Responda em até três frases.”
• Formato: “Use uma lista com três recomendações.”
• Objetivo: “Recomende produtos com base nas necessidades do cliente.”

• Mudar o tamanho do LLM: pode alterar capacidade e custo, mas não garante idioma ou respostas curtas.
• Aumentar a temperatura: aumenta a criatividade e a aleatoriedade; não controla diretamente o tamanho ou idioma.
• Aumentar o Top K: permite considerar mais tokens prováveis, aumentando a variedade; também não é o mecanismo principal para controlar idioma ou comprimento.

• B: Moving the task may affect the critical path and should not be done before evaluating the planned response and impacts.
• C: Excluding a required task is not appropriate without formal analysis and stakeholder approval.
• D: Lessons learned and the risk log should be updated, but only after or alongside managing the immediate issue; updating them is not the first action.

• Le rôle n’a pas de clés propres. Des identifiants temporaires (via STS) sont émis lorsque quelqu’un ou quelque chose « assume » le rôle.
• La trust policy déclare qui peut assumer le rôle (par ex. une instance EC2, un utilisateur IAM, ou un service comme Lambda).
• Une fois attaché à une ressource (par exemple comme un instance profile sur une EC2), l’application peut appeler les services AWS avec les permissions du rôle.

• Respect du principe du moindre privilège: on accorde uniquement ce qui est nécessaire.
• Pas de stockages de clés sur les instances; les credentials se renouvellent automatiquement.

• Rôles pour EC2, rôles pour Lambda, accès cross-compte, etc.

• Vertical scaling (scale up) means increasing the size of an existing VM—for example, adding CPU or RAM.
• Vertical scaling down means reducing the VM’s size when less capacity is needed.
• Horizontal scaling (scale out) means adding more VM instances rather than making one VM larger.
• Elasticity is the broader ability to automatically adjust resources based on demand; it does not specifically mean adding CPU or memory to one VM.
• Agility refers to the ability to provision or change resources quickly.

• Assignment
• Decision
• Get Records
• Loop

• Screen flow: Would include a Screen element.
• Inactive version: Inactive status does not restrict the available elements.
• Activated version: Activation status also does not determine the toolbox contents.

• S3 Lifecycle rules automate actions such as transitioning objects to different storage classes or deleting old objects.
• S3 bucket policies control access permissions; they do not preserve earlier object versions.
• S3 server-side encryption protects data confidentiality by encrypting objects at rest, but it does not prevent deletion or overwriting.

• Accidental deletion or overwriting ? S3 Versioning
• Unauthorized access ? bucket policies and IAM
• Data encryption ? server-side encryption

• Secure: uses encryption, such as HTTPS or SFTP.
• Cross-platform: supported by many languages and operating systems.
• Internet-friendly: designed to communicate across networks, usually using standard Internet protocols.

• JSON/REST over HTTPS — widely supported, secure, and Internet-friendly.
• SOAP over HTTPS — also secure and highly cross-platform, though more heavyweight.
• XML over SFTP — secure file-based exchange, but it is not an API-style interface.

• Product Owner: May attend, but is not required unless also working as a Developer.
• Scrum Master: May attend to help facilitate or coach, but is not required.
• Developers: Must participate because the event is specifically for them.

• IaaS provides virtualized infrastructure, including VMs, disks, and networking. You manage the guest operating system and software installed on the VM.
• PaaS provides a managed platform for deploying applications without managing the underlying VMs or operating systems. Examples include Azure App Service and Azure Functions.

kusto 
Event | where EventType == "error"

• == is the KQL equality operator.
• -eq is a PowerShell operator, not KQL.
• is is not the correct equality operator in this context.

text 
Event | where EventType –eq "error"

• Event | search "error" — valid, broad search.
• search in (Event) "error" — valid, broad search.
• Event | where EventType == "error" — valid, targeted filter.

1. The sender hashes the original message and sends the message plus its hash.
2. The receiver applies the same hashing algorithm to the received message.
3. The receiver compares the newly calculated hash with the sender’s hash.
4. Matching values indicate that the message was not altered in transit.

• A binary image is not the normal description of a hash result.
• Using a different algorithm produces a different type of digest, so the values cannot be directly compared.
• Hashing verifies integrity, but by itself does not prove who sent the message. Digital signatures or MACs address authentication and integrity together.

• You normally do not create a new sensitive information type for credit card numbers. Microsoft Purview already provides a built-in Credit Card Number sensitive information type.
• The required sequence should generally be:

1. Determine which host was infected first—the originating host.
2. Decide whether each other host is clean or infected based on communication and event logs.

• Compare timestamps and find the earliest suspicious event.
• Look for the host that initiated the malicious connection, file transfer, exploit, or command—not merely a host that later received traffic.
• Follow the timeline through the firewall:

• A host is likely infected if it both receives suspicious activity and then initiates related malicious traffic.
• A host may be clean if the firewall blocked the connection and there is no evidence of execution or follow-on communication.

• Planning — identify the need, objectives, resources and feasibility.
• Analysis — determine user requirements and examine the existing system.
• Design — specify how the new system will work.
• Implementation — build, test, install and introduce the system.
• Maintenance/evaluation — monitor and improve the system after implementation.

kusto 
Event 
| summarize make_set(EventID) by Computer

• summarize groups records.
• by Computer creates one result row per virtual machine.
• make_set(EventID) returns an array containing unique event IDs for that computer.

kusto 
| summarize make_list(EventID) by Computer

• You provision the virtual machine.
• You manage the guest operating system, applications, and configuration.
• Azure manages the physical servers, datacenter, and underlying virtualization infrastructure.

• Use one Azure AD directory for the organization.
• Separate divisions with subscriptions and/or resource groups.
• Assign each division’s administrator appropriate Azure role-based access control (RBAC) permissions, scoped to their subscription or resource group.

• Correct answer: A) Hashing

• Why: Hashing produces a fixed-size digest of the software. If the final build is altered in any way, the hash will change, enabling you to detect tampering by comparing the stored digest with a freshly computed one.

• Why not the others:

• Aggregation happens once, during the scheduled job.
• Dashboard users query a relatively small, precomputed table.
• Repeated users do not trigger expensive aggregations against the detailed sales table.
• Overwriting is appropriate because the summary is rebuilt for the reporting period.

• B: Structured Streaming is unnecessary for data that only needs daily refreshes and adds operational/compute overhead.
• C: A view recomputes the aggregation at query time, increasing latency and query cost.
• D: Delta caching may improve reads but does not replace the need to materialize the expensive aggregation, and cache availability is not the main design guarantee.

• The first step in risk management is to understand objectives, constraints, and drivers from those who care about the project. This stakeholder engagement helps identify what could go wrong and what risks are most critical.
• Only after you’ve gathered input from stakeholders should you identify risks and document them in the risk register. Updating the risk register (option C) is important, but it comes after identifying and analyzing risks.
• Options B (ensure resources) and D (revise the risk management plan) are actions that may follow once risks are identified and understood; they’re not the initial step.

• B. Data loss prevention (DLP): Helps prevent sensitive data from being copied, emailed, or exfiltrated. It is not the primary control for protecting a stolen laptop’s stored data.
• C. Operating system hardening: Reduces vulnerabilities by disabling unnecessary services and applying secure settings, but it does not necessarily protect the files if the disk is accessed directly.
• D. Boot security: Helps ensure the device starts only through trusted software or approved processes. It supports platform integrity but does not itself encrypt stored files.

• Microsoft Teams: Connects to Teams-related data, but it isn’t the primary connector for the Power Apps data tables.
• Personal Analytics: Provides personal productivity insights, not application data.
• SQL Server database: Only applies if the app explicitly uses SQL Server as its data source.
• Dataflows: Used for preparing and centralizing data, not as the normal direct connection to a Power Apps app.

• Multiple nodes: Data is replicated several times in the primary region.
• Separate geography: A copy is asynchronously replicated to a secondary Azure region.
• Readable secondary: RA-GRS provides read-only access to the secondary replica, even when the primary region is available.

• GRS: Replicates to another region but the secondary copy isn’t normally readable.
• ZRS: Replicates across availability zones in the same region, not a separate geographic region.
• LRS: Keeps replicas within a single datacenter or region and provides no geographic redundancy.

• IPsec: Protects traffic at the network layer, commonly for VPNs; it is not WPA2’s authentication protocol.
• SSL: Protects specific application sessions and has largely been replaced by TLS.
• SSH: Secures remote command-line administration.

json 
{ 
  "Effect": "Deny", 
  "NotAction": [ 
    "iam:*", 
    "route53:*", 
    "cloudfront:*", 
    "support:*" 
  ], 
  "Resource": "*", 
  "Condition": { 
    "StringNotEquals": { 
      "aws:RequestedRegion": "eu-west-1" 
    } 
  } 
}

• SCPs set maximum permissions; they do not grant permissions. The default SCP allows actions, so the restriction must be an explicit Deny.
• aws:RequestedRegion checks the Region targeted by an API request.
• StringNotEquals: eu-west-1 denies requests directed to every other Region.
• NotAction allows designated global services to remain usable because they do not operate in a single AWS Region.
• Attaching the SCP to the OU makes it apply to existing accounts and accounts later added to that OU.

• B. Enable column profile — This turns on column profiling, which computes statistics like min and max for each column.
• C. Show column profile in details pane — This ensures the per-column profile is visible in the details pane.
• E. Enable details pane — This makes the details pane available so you can view the column profile there.

• A. Show column value distribution may help with distribution but isn’t specifically about min/max.
• D. Show column quality details shows data quality (valid/null counts), not min/max.

Flat organisation

• Few levels of management
• A wide span of control—managers supervise many employees
• Shorter communication channels
• More employee autonomy and quicker decisions
• Fewer formal promotion levels

Tall organisation

• Many levels of management
• A narrow span of control—managers supervise relatively few employees
• A clear hierarchy and reporting structure
• More formal supervision and communication channels
• More obvious promotion and career stages

• Whether a user has a console password
• Password age and last password change
• Whether MFA is enabled
• Access key status
• Access key creation date and last-use information
• Access key age, which helps audit rotation

• IAM Access Analyzer identifies unintended access to resources; it does not report credential age or rotation.
• AWS Artifact provides AWS compliance documents and agreements, not details about your IAM users.
• AWS Audit Manager helps collect evidence for audits, but it is not the direct tool for viewing IAM credential rotation details.

• Regional leads — Customer Community Plus

• Capacity planners — External Identity

• Customer Community does not provide the enhanced reporting/dashboard access required by regional leads.
• An Identity license is generally for internal Salesforce identity use and does not fit the external capacity-planning users as well as External Identity.

• Workspace: Stores notebooks, libraries, jobs, and other project resources.
• Notebooks: Interactive documents containing code, queries, visualizations, and explanations. Common languages include Python, SQL, Scala, and R.
• Clusters: Groups of virtual machines that run Spark workloads. Clusters can be started, stopped, and automatically scaled.
• Data access: Databricks can read from services such as Azure Data Lake Storage, Azure Blob Storage, and Azure SQL.
• Jobs: Automate notebooks or data-processing workflows on a schedule or in response to events.

• A. IDS attack signatures: An IDS primarily detects suspicious network activity and usually alerts rather than directly scanning and blocking uploaded files.
• C. Load balancer: Distributes traffic among servers but does not inspect files for malware.
• D. WAF: Protects web applications from attacks such as SQL injection, cross-site scripting, and some malicious requests. It is not primarily a PDF-malware scanning solution.

• Numerical flexibility: Adjusting the number of employees, such as using temporary, part-time or contract staff.
• Temporal flexibility: Varying when employees work, such as through flexitime, overtime or different working hours.
• Shift system flexibility: Changing work patterns or shift arrangements; it is not specifically about moving between tasks.

1. Modify the database subnet NACL inbound rules to allow traffic from the new web subnet’s CIDR block on the MySQL port (3306).
2. Modify the database subnet NACL outbound rules to allow return traffic to the new web subnet’s CIDR block on the required ephemeral port range.

• The user authenticates with the external Identity Provider.
• Salesforce receives the SAML assertion.
• Salesforce uses attributes in that assertion—such as username, email, first name, last name, and profile/community information—to create the user during the first login.
• On later logins, Salesforce updates or uses the existing user record.

• On-the-fly provisioning is a general phrase; the Salesforce capability being tested is specifically JIT provisioning.
• Salesforce APIs would require a separate integration and provisioning process.
• Identity Connect is designed primarily to synchronize users from an identity directory, not to create users at the moment of their first SAML login.

• Date: 2018-12-31
• Time: 08:59

• B: The original value contains the text at, so it cannot be converted directly to a date.
• A: The last characters contain the time, not the date.
• D: Extracting the first 11 characters can leave an unwanted space and does not properly separate the time component.

• Reusing features across different models and teams
• Consistent feature definitions
• Managing feature versions and metadata
• Using features for both training and inference

• SageMaker Data Wrangler: Prepares and transforms data; it is not primarily a shared feature repository.
• SageMaker Clarify: Helps detect bias and explain model predictions.
• SageMaker Model Cards: Documents models, including intended use, risks, and evaluation results.

• The 99.99% availability SLA for VMs is achieved when you run VMs across two or more Availability Zones.
• Two VMs in a single Availability Zone do not meet the 99.99% target (their SLA is lower, e.g., around 99.95% or less depending on configuration).

• Deploy at least two VMs across two different Availability Zones (one VM in each zone, or both in two zones with a load balancer).
• This provides the required zone redundancy and the 99.99% SLA.

• View/inspect configuration: Possible.
• Modify the installed application or its S-Controls: Typically restricted in a test-drive org.

1. Ingestion Lambda receives requests from API Gateway and places messages in an SQS queue.
2. Processing Lambda is triggered by the queue and loads records into Aurora PostgreSQL.

• Decoupling: API request handling is separated from database loading.
• Buffering: SQS absorbs bursts when incoming traffic exceeds the database’s processing capacity.
• Controlled concurrency: Configure the SQS-triggered Lambda’s concurrency and batch size to avoid overwhelming Aurora or exhausting database connections.
• Automatic retries: Messages that fail processing can return to the queue and be retried. A dead-letter queue can capture persistent failures.
• Lower operational effort: The solution remains serverless and avoids managing EC2 servers or Kubernetes clusters.

• A: EC2 and Tomcat add server-management overhead.
• B: DynamoDB/DAX would require changing the database model and does not solve the Aurora ingestion design.
• C: SNS is useful for notifications and fanout, but SQS is better for durable buffering and backpressure in this producer-consumer workflow.

• C — “when the query finishes”

• D — “when the query began”

• The files are stored in a document library, which is exposed through the SharePoint Folder connector.
• The connector returns file metadata, including Folder Path, Name, and Content.
• In Power Query, filter Folder Path so only files in the manufacturing reports folder are retained.
• You can then combine the remaining Excel files because they all have the same structure.

• SharePoint List is for SharePoint lists, not document-library files.
• Combine & Load combines files immediately, before you filter to the required folder, and may include unwanted files.
• Transform gives you the opportunity to filter the file list first, which is more efficient and targeted.

• The correct AAA mapping (per Cisco objectives) is:

• Why the given options aren’t fully correct:

• Quick takeaway: when you configure AAA, you should conceptually map them as:

• Example commands (to reinforce concepts):

• Used for communication on the local link or LAN segment
• Automatically generated on IPv6-enabled interfaces
• Not routed by routers to other networks
• Commonly used by devices to communicate with their local IPv6 router
• Begins with FE80 through FEBF

• FC00::/7 — unique local unicast
• FE80::/10 — link-local unicast
• FF00::/8 — multicast
• 2000::/3 — global unicast

• Basic: billing/subscription support only; no technical support requests can be opened.
• Developer, Standard, Professional Direct, and Premier: include technical support and allow opening new support requests.

• If option A corresponds to “Developer, Standard, Professional Direct, Premier,” that is the correct choice.
• If the option text is really “Premier only,” that would be incorrect per current Azure docs.